In adaptive (Agile) project management, maintaining a steady and predictable Velocity is crucial for delivering an MVP within a fixed number of sprints. According to the Agile Practice Guide and lean manufacturing principles integrated into Agile, " Context Switching " is one of the primary " wastes " that destroys productivity.
Why Choice D is correct:
The Cost of Task Switching: When team members are forced to multitask (switching between different projects or unrelated tasks), there is a significant mental " restart " cost. Research often cited in Agile literature suggests that multitasking can lead to a loss of up to 20% to 40% of a person ' s productive capacity due to the time lost re-focusing on different contexts.
Impact on Flow: Agile teams thrive on " Focus, " one of the five Scrum values. By introducing multitasking in the third sprint, the team ' s ability to maintain a flow state was broken, leading to the dramatic 30% drop in productivity described in the scenario.
Analysis of other options:
A (Working in silos): While silos are inefficient and discourage collaboration, they usually lead to quality issues or integration delays rather than a sudden, sharp 30% drop in overall productivity in a single sprint.
B (Measuring velocity for the first time): Measuring velocity is a data-gathering activity. The act of measuring does not inherently cause productivity to drop; it simply makes existing productivity visible.
C (Technical debt): Picking up technical debt items actually counts toward the work completed in a sprint.
While technical debt makes future work slower, addressing it in the current sprint is a planned activity and wouldn ' t cause a " loss in productivity " relative to the work assigned; it would simply be the work the team chose to do.
Key Concept: The PMBOK Guide and Agile methodologies emphasize the importance of dedicated teams.
In an adaptive environment, a Project Manager (or Scrum Master) must protect the team from external interruptions and multitasking to ensure the Sustainable Pace required to hit the MVP deadline. Choice D represents a common management error that violates the principle of focused, iterative delivery.