Cycle Time Mapping & Evolving from Story Points by Scott Aucoin
Cycle Time Mapping & Evolving from Story Points
We’ll start with a thorough overview of Cycle Time Mapping – the process of quantifying how quickly and effectively teams move units (stories, chores, bugs… anything) through the workflow from start to finish. We’ll cover: “How to” for setup, mapping out the full process, focusing on individual workstreams to improve cross-functional team balance and avoid bottlenecks, quantifying the increase of time due to handoffs or hand-backs (ie, PO rejecting a story), finding averages based on story points, and showing the overall value of time for forecasting, planning, and resource management.
After the deep dive into cycle time & analysis, we’ll put that info straight to work by looking at the value of story points. We’ll review how your team averages out over time and then use that average to remove the waste that estimation creates without adding risks. Cycle times are the first step toward a more lean estimation and planning process that is accurate and works hand-in-hand with other agile and lean reporting tools (like burn-up and burndown charts). The audience will walk away with knowledge of how to setup their own cycle time collection, how to analyze the numbers, and how to move their teams to a more lightweight estimation and planning process (giving their team more time to work, aka better velocity).
0-10 mins: Cover traditional scheduling/forecasting approaches and flaws
11-25 mins: Setup of cycle time mapping (tools, and getting the right data)
26-55 mins: Analysis of data, reviewing real world charts and how to use that data to improve decisions, team makeup, processes, and inform appropriate executive decisions (this will include the metrics listed in the abstract, such as: Time by point [fibonnaci sequence], time increase due to handoff, identifying bottlenecks by workstream [and stalls in the process], general averages for each unit, and so on). All numbers are taken from actual teams and each will have different examples of the results that they can drive.
56-65 mins: Review the statistics around avg units (stories, chores, bugs) and how to set a baseline for estimation/expectations.
66-80 mins: Taking the baseline from the avg units and putting that to work to replace the waste created from Story Point estimates - giving time back to skilled team members to do what they do best, forecast more effectively, and provide executives/stakeholders with better data for their planning purposes.
81-90 mins: Q & A
|Constraints and Class Arrangement||
This talk is designed for an intermediate or above group. Beginners in the Agile community may find more benefit from focusing on the value of story points before seeing the value in evolving away from them. No other constraints or arrangement needs aside from the obvious (projector/screen, podium, chairs, etc.).
This session is being pitched to several conferences between May and August and will hopefully have been delivered to a few. At the very least it will be delivered to the Chicago Agile Open Space as well as the Chicago Agile Methodology Meetup. The methods have been tested and vetted with seasoned pros, and the speaker has talked at other conferences.
|Last Updated||16 Aug 14:09|