Timeline for How do you explain to an "agile" team that they still need to plan the software they write?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2011 at 14:54 | comment | added | Steven A. Lowe | +1 excellent answer. The story is the goal - it is the tip of the iceberg, a placeholder for a future conversation, the first step on the journey; it is not the entire journey! The test descriptions are the requirements, use-cases, and acceptance criteria combined. Design is not ignored, design is scope-limited to the story and the tests, but do as much design as you need to. Anyone skipping design and claiming that's the agile way either doesn't understand (go read the XP book again), doesn't want to (cowbow coding yee-haw!), or is just being lazy. And giving Agile a bad name. | |
| May 22, 2011 at 11:20 | history | edited | Ladislav Mrnka | CC BY-SA 3.0 | added 162 characters in body |
| May 22, 2011 at 10:47 | history | answered | Ladislav Mrnka | CC BY-SA 3.0 |