Agile, Scrum, and “Hitting the Date”

Agile, Scrum, and “Hitting the Date” examines a common objection to Agile development: “We can’t use Agile here because we have to hit dates.” The paper argues that this objection rests on a misunderstanding of Agile. Scrum is inherently time-oriented, with fixed Sprint boundaries and longer planning horizons built from Sprints. The real challenge is not whether Agile can work with dates, but how an organization manages scope, resources, and uncertainty when the date matters.

The paper challenges another common Agile misconception: that every Sprint must produce a new, usable product feature. Instead, a Scrum Team completes and tests a defined set of deliverables during each Sprint, with the sequence of work chosen according to value and dependencies. This distinction is particularly important in hardware development, where many useful capabilities require multiple Sprints to develop and where physical deliverables may take substantial time to produce.

The paper then compares traditional project scheduling with Agile long-term planning. It describes how Release Planning creates a medium-term plan that maps deliverables to Sprints and teams while making cross-team dependencies visible. A hybrid Release Plan illustrated in the paper combines Scrum teams with a predictive team using traditional project scheduling, demonstrating that Agile planning does not require every participating group to abandon its existing planning approach.

The paper's central approach to fixed dates is to manage scope rather than simply demand that all planned work be completed. When a date cannot move, teams can reserve capacity for unexpected work and adjust scope while preserving the underlying business objective. The paper argues that a business goal should not be equated with a particular predefined scope; different technical solutions may achieve the same goal with different levels of cost, complexity, and development time.

The result is a practical perspective on how Agile organizations can improve their ability to meet important dates despite uncertainty. Whole-team participation in planning and estimation, deliverable-oriented Release Plans, frequent inspection of progress, and the ability to adapt scope provide mechanisms for responding to problems without simply pushing the delivery date.