Chapter 12: Plans theme Flashcards
Purpose of Plans Theme
Facilitates communication & control
Defines how, where, when, and by whom products will be delivered
PRINCE2 Plan Levels
Project Plan
Stage Plan
Team Plan
Exception Plans: Replace an existing plan if needed
Agile Planning Emphasis
Planning based on experience (empiricism)
Planning & estimating with techniques like story points
Flexible approach suited to different Agile frameworks
Empirical vs. Rational Planning
Empirical: Based on past performance (e.g., velocity, yesterday’s weather)
Rational: Based on logic & reasoning
Agile Planning Style
Requirement & feature-based (not phases like design/build)
Team-driven for ownership & self-organization
Just-in-Time (JIT) Planning for flexibility
Using Points in Agile Planning
Can use story points or lead times
Timeboxed approach (e.g., Scrum) vs. Flow-based approach (e.g., Kanban)
Points should be used as a guide, not a rule
PRINCE2 & Agile Planning Approaches
Supports Gantt charts or backlog-based planning
Collaborative planning improves responsiveness
Empiricism helps balance predictive vs. adaptive planning
Planning Horizons
Short-term = Detailed, accurate
Long-term = Less detail, higher uncertainty
Uses tolerances to account for uncertainty
Emergent Planning in Agile
Planning evolves as the project progresses
Avoid over-planning → Just Enough Planning (JEP)
Product-Based Planning in Agile
Plans around features & user stories
Avoids technical phases (design, build, test)
Minimum Viable Product (MVP) focus
Sprint Planning Considerations
Prioritization is key
Dependencies & similar work must be considered
Balance between predictive (PRINCE2) & adaptive (Agile)
Agile Estimation Techniques
Relative Estimation (comparing tasks to each other)
Story Points (Fibonacci sequence: 1, 2, 3, 5, 8, etc.)
T-shirt Sizing (Small, Medium, Large, XL)
Planning Poker (team voting for estimates)
