Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 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. Commented Oct 11, 2016 at 12:26
  • @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. Commented Oct 11, 2016 at 12:40