Timeline for Does Scrum need System specification document?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 9:51 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 | deleted 36 characters in body |
| Oct 11, 2016 at 12:40 | comment | added | Thomas Owens♦ | @AlanLarimerPSM I'm familiar with why the creators of Scrum chose to focus on other aspects of projects. However, that lack of consideration for any pre-project rituals leaves a lot of questions in the eyes of people implementing Scrum. Sprint 0 is a common solution to this, but both Disciplined Agile Delivery and Scaled Agile Framework provide guidance for how to implement these activities in a manner consistent with the principles of agile and lean methods - they don't need to be cumbersome or reduce competitive advantage, but will also yield a higher quality product. | |
| Oct 11, 2016 at 12:26 | comment | added | Alan Larimer | I strongly recommend Software in 30 Days for a better understanding of why the Scrum framework and other agile paradigms do not include a classic Project Inception phase. Here are some brief points. Agile software development is about reacting to opportunities; cumbersome pre project rituals reduce competitive advantage. Scrum focuses on products and not projects which is an important distinction. Short iterative and incremental efforts, each resulting in a potentially releasable product, is risk management. | |
| Oct 10, 2016 at 13:20 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |