Essential Scrum – Scrum Planning Principles & Multilevel Planning (8)
Scrum Planning Principles
Focus on adapting and replanning
Favor smaller releases
The idea is that with smaller releases the functionality reaches the user faster and you can breakeven earlier than expected.
Portfolio planning (or portfolio management) is an activity for determining which products to work on, in what order, and for how long. Although portfolio planning is conceptually at a higher level than product planning (because it deals with a collection of products), one of its primary inputs is a newly envisioned product idea from product planning.
Product Planning (Envisioning)
The goal is to capture the essence of a potential product and to create a rough plan for the creation of that product. Envisioning begins with the creation of a vision, followed by the creation of a high-level product backlog and frequently a product roadmap.
Product planning consists of:
- Product vision
- High-level backlogs
- Product roadmap
Release planning is about making scope, date, and budget trade-offs for incremental deliveries. A simple way to visualize a release is to draw a line through the product backlog (see Figure 15.3). All of the items above the line are planned for the release, and all of the items below the line are not planned for the release. This line can move up or down in the product backlog as you gain better insight into the product.