Adaptive Planning
Core Concepts
Adaptive planning is iterative and incremental, embracing change as new information emerges. Key practices include rolling wave planning, progressive elaboration, and just-in-time planning. In Agile, planning occurs at multiple levels: release planning, sprint planning, and daily planning. The product backlog is continuously refined (backlog grooming). Estimation techniques include story points, planning poker, and relative sizing. Velocity and burndown charts help forecast. Candidates must understand the difference between predictive (waterfall) and adaptive planning, and when each is appropriate.
Traps
A common trap is over-planning upfront. Questions may ask how to handle a change mid-sprint; the Scrum Master should protect the sprint goal and negotiate with the product owner for future sprints, unless the change is critical. Another trap is using velocity as a performance metric rather than a forecasting tool. Also, beware of answers that fix scope and date without adjusting resources or quality-the iron triangle trade-off.
Worked Example
A team is asked to commit to a fixed date for a set of features. Instead of promising all features, they use velocity to forecast and propose a minimum viable product (MVP) by the date, with additional features in later releases. This demonstrates adaptive planning by adjusting scope to meet the date while delivering value early.
Rule of Thumb
Plan enough to start, then inspect and adapt; keep plans lightweight and updated frequently.