You are facilitating a project using a hybrid approach where requirements are gathered upfront but development occurs in two-week iterations. After four iterations, the team's velocity has been inconsistent: 28, 15, 32, and 18 story points respectively. The team reports that some iterations include significant work on technical infrastructure that doesn't directly relate to user stories but is necessary for the architecture. The project sponsor is concerned about the unpredictable pace and asks why the team cannot maintain consistent velocity. How should you address this situation?

Question

Accepted Answer

The correct answer is B. Capacity allocation acknowledges that sustainable delivery requires ongoing technical work alongside features, and explicitly planning for it (e.g., reserving 20-30% of capacity) creates more predictable velocity while ensuring necessary technical work is not neglected. This approach makes invisible work visible and allows for more realistic planning and stakeholder expectations. It aligns with agile principles of sustainable development and technical excellence. Option C applies a statistical band-aid without addressing the underlying cause of velocity variation. Option A creates technical debt and will slow future feature development, ultimately reducing overall value delivery. Option D increases complexity and coordination overhead while potentially creating integration challenges between the parallel tracks.

More Process Questions