Timeline for How do you prioritize initial sprints to maximise the chance of catching architecture errors early?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2015 at 8:22 | vote | accept | Bob Tway | ||
| Jan 21, 2015 at 17:42 | comment | added | Frank Hileman | @MattThrower Perhaps the developers simply lack experience. | |
| Jan 15, 2015 at 19:54 | comment | added | Bob Tway | Actually, they did iterate. That's partly what's so scary about the situation this project is in. They just showed the wrong things when they were iterating - picking off the low-hanging fruit and treating interlinked things as isolated issues so users couldn't see an end-to-end process. Avoiding a repeat of this time-wasting exercise is what I'm so keen to avoid. This is still excellent advice, mind, so +1, thanks. | |
| Jan 15, 2015 at 19:42 | history | answered | Telastyn | CC BY-SA 3.0 |