My friend and sometimes colleague John Heintz asked me to play the straight man in his first experiment in professional video blogging. John is a powerful advisor to many agile and lean software engineering teams, managers, and executives around the world and he described the collaborative planning concept as something that he's "drawn on a whiteboard over a hundred times."
|Photo courtesy of rofi/flickr|
Protip: when you're planning work around a user story, don't try to model dependencies, just assign a number of story points or hours in a bucket, and let the work flow naturally, allowing the work to be the focus as opposed to the plan or the team member allocation. Monitor the work on a daily basis.
Protip: if you're 40% through your sprint (e.g. the fourth day of a ten day sprint), and all or most stories are in progress and nothing is done yet, you're likely in "Scrumfall" and you are likely performing sequential versus collaborative planning.
Without further ado, here's our first experiment together in video blogging around the benefits of a collaborative planning model:
Here's his full blog post: http://gistlabs.com/2013/09/video-sequential-and-collaborative-planning/
Does this concept resonate with you? What has been your experience?