Agile planning is continuous rather than a single planning event completed once.
The source material emphasizes multiple planning levels, collaboration with customers and teams, frequent demonstrations, and value-based prioritization.
Value-based prioritization
When every item cannot be done immediately, ask:
- Which item creates the most value?
- Which item reduces important risk?
- Which item unlocks other work?
- Which item is needed for a meaningful release?
- What is the cost of delaying it?
Prioritization techniques
The material discusses collaborative techniques such as:
- Dot voting / multi-voting
- Monopoly-money style allocation
These techniques make stakeholder priorities visible and create a basis for discussion.
Backlog refinement
A backlog should remain understandable and prioritized.
Refinement can include:
- Clarifying requirements
- Splitting large items
- Removing obsolete work
- Updating priorities
- Adding acceptance criteria
- Identifying dependencies
Spikes
A spike is a focused investigation used to learn something important before committing to implementation.
Examples:
- Architecture proof of concept
- Risk investigation
- Technical feasibility exploration
Portfolio exercise
Create a prioritization matrix using:
Value × Risk Reduction × Urgency × Effort
Clearly label the matrix as a personal learning artifact rather than a PMI-prescribed scoring formula.