RLC Events Don't Move: Three Ways the Rapid Lea...
I met with a program team this week that experienced a delay when the group was assigned to help out another project team. That led to some fruitful discussions about how to handle such a delay. In a traditional product development program, the date just slips, and it may not be visible to everyone that this has happened until weeks or months down the road.
In a Rapid Learning Cycles program, we don't assume that a program delay like this will change the schedule. The Learning Cycle and Integration Events still take place on schedule.
The team and stakeholders may decide to delay the program - but they do that by adding additional Learning Cycles - not by extending the cadence of Rapid Learning Cycles or delaying Events. In fact, a team in trouble is the kind of team that benefits the most from holding the Events on time.
This week's Knowledge Brief describes how the Rapid Learning Cycles Framework reinforces project timelines so that product teams stay on track to deliver on time.
- In a traditional product development program, project updates and gate reviews get delayed until the team is ready for them.
- In the Rapid Learning Cycles framework, Learning Cycle and Integration Events are fixed in time, and teams hold these events whether or not they feel “ready” to have them.
- Teams that are having problems are the ones that most need these events to be on time.
Rapid Learning Cycle Events Don't Move: Three Ways the Rapid Learning Cycles Framework Reinforces Project Timelines
This Knowledge Brief may be freely distributed without modifications in its original PDF form, including all authorship, copyright and contact information. Other uses require our explicit permission.
posted Jul 5, 12:46 am (869 days ago)