Timeline for UI/UX design feels like waterfall, What do you think should be the proper process?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14 at 20:02 | answer | added | Scott Hannen | timeline score: 0 | |
| Aug 1, 2022 at 13:53 | answer | added | Ewan | timeline score: 0 | |
| S Aug 1, 2022 at 12:56 | review | Close votes | |||
| Aug 6, 2022 at 3:07 | |||||
| Aug 1, 2022 at 12:50 | vote | accept | Guiom | ||
| Aug 1, 2022 at 12:44 | answer | added | Thomas Owens♦ | timeline score: 4 | |
| Aug 1, 2022 at 12:33 | comment | added | Doc Brown | The proper course is to ask your team (which includes all the roles you mentioned). Strangers from the internet are unlikely to know how your team can improve. | |
| Aug 1, 2022 at 12:12 | comment | added | jonrsharpe | That is waterfall. You've tagged this agile but in what you've described the only feedback cycle is UI/UX diffs -> bugs. Do the devs have input to the design process in terms of what's feasible (e.g. what components are in libraries already in use)? Do you and QA have a shared understanding with design and the stakeholders about what's important in the template, vs. what might just be nice-to-have? Do you have any mechanism to iterate towards a good-enough implementation rather than spending effort on fixing "bugs" that the stakeholder may not even care about? | |
| S Aug 1, 2022 at 12:04 | review | First questions | |||
| S Aug 1, 2022 at 12:56 | |||||
| S Aug 1, 2022 at 12:04 | history | asked | Guiom | CC BY-SA 4.0 |