Scrum in a Fixed-Date Environment

Author(s): Paul Given
Venue: Scrum Alliance
Date: 04/06


Scrum Size: 12-15
Sprints: 30 days
Scrum Meetings: Bi-weekly
First Time: Yes
Overall Transition: worked well

There is a notion that a fixed date product is more suited for a waterfall process and an Agile process is
too unstructured. However it is often the case that a tester will find an issue two weeks before go live
on a waterfall project and no one knows how to trace the issue. This team transitioned into using a
Scrum process and found immediate positive results.

The team was able to quickly review documents and create requirements and move through four
iterations. The work was finished and system testing was completed 45 to 60 days in advance of the
release date.

Several factors that were key to their success was the strong use of team collaboration, multi-level
scrums, and visual tools. The teams were not co-located so they were not able to do daily scrums, but
bi-weekly scrums worked well enough. Team collaboration and requirements development allowed
each person to understand the overall system and offered solutions on how to get features done easily.
It also allowed the impact of any change to the system to be understood by all members of the team