Timeline for What document/diagram is must have for a software project?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2012 at 11:50 | comment | added | Juraj | Regarding the Agile project I think there is a need for similar document too, but some of the parts don't have to be filled in at the beginning. PRD is quite high-level document, in agile world more than in waterfall one. And it is more open to changes in agile world. But I think even project that is agile have to have clear high-level idea about what should be the results of the project, who are the actors, when should be the project delivered, etc. Maybe PRD is not the correct title for agile project... | |
| Mar 11, 2012 at 0:44 | comment | added | MathAttack | One thing I find useful in this doc is the business case. This helps prioritize the requirements. | |
| Mar 10, 2012 at 0:06 | comment | added | Michael Durrant | and that's a real shock to traditional waterfall style developers who have a hundred reasons why it sounds crazy. I know I did before I got into it. | |
| Mar 10, 2012 at 0:05 | comment | added | Michael Durrant | there are no musts as is evident in Agile projects which would have little of the above. | |
| Mar 8, 2012 at 10:12 | history | answered | Juraj | CC BY-SA 3.0 |