Stop Starting. Start Finishing - ProductCampAustin10 - PCA10

Editor's Notes

• #4: Couple questions?Who is working with software development teams?Who is employing Agile Methods?Who is using Scrum?Who is using Kanban?Who has heard of Kanban before?Give aways at the end. Let them choose which class they want a 50% discount on. Random person and who tweets
• #5: Many software companies are drowning in a sea of opportunity and instead of focusing on getting the highest value items done we are crippled by trying to do too much at one time.http://www.123rf.com/photo_8127859_single-hand-of-drowning-man-in-sea-asking-for-help.html
• #6: 3m
• #7: What is the impact of change in the left vs the right?Change – underestimatedChange – new high priority requirementWhich plan will have the biggest impact if there is a change?
• #9: 15 minsTeam breakout then highlights as a group
• #10: 15 minsTeam breakout then highlights as a group
• #11: 15 minsTeam breakout then highlights as a group
• #12: http://www.123rf.com/photo_7850401_young-male-student-is-overwhelmed-by-way-too-many-homework-assignments.htmlRequestsLack of resourcesDon’t trust that project will ever get started (maybe that is the right business decision)Sr leadership not setting priorities
• #15: http://twinpowerment.blogspot.com/
• #17: Why waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
• #18: Set the rate at which we accept new requirements into our software development pipe to correspond with the rate at which we can deliver working code.Once you balance demand against throughput and limit the work-in-progress within your value stream, magic will happen. Only the bottleneck resources will remain fully loaded. Very quickly, other workers in the value stream will find they have slack capacity. Meanwhile, those working in the bottleneck will be busy, but not swamped. For the first time, perhaps in years, the team will no longer be overloaded and many people will experience something very rare in their careers, the feeling of having time on their hands.Limit WIP in andLevel Flow will:Expose the bottlenecksEnable improvementSimplifies prioritizationWhy waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
• #19: Need to throttle the input (demand) into the system
• #20: The slack capacity created by the act of limiting work-in-progress and pulling new work only as capacity is available will enable improvement no one thought was possible.By throttling the input (demand) into the systemThis will limit the Work In Progress and Level Flow Which will expose the bottlenecksAnd enable improvementOnce you balance demand against throughput and limit the work-in-progress within your value stream, magic will happen. Only the bottleneck resources will remain fully loaded. Very quickly, other workers in the value stream will find they have slack capacity. Meanwhile, those working in the bottleneck will be busy, but not swamped. For the first time, perhaps in years, the team will no longer be overloaded and many people will experience something very rare in their careers, the feeling of having time on their hands.Limit WIP in andLevel Flow will:Expose the bottlenecksEnable improvementSimplifies prioritizationWhy waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
• #22: Does this feel like the dev process? Dev and QA?
• #23: Do we ever have any built up queue in front of QA?Gets continually slower
• #24: Slow down A to 5 items/ min (reduce Dev resources)Put B before A Double B Resources (hire more QA)Reallocate resources from A to B to level the flow (TDD or Dev help QA?)
• #25: Prioritization is no longer about ordering all the WIP or all initiatives but picking the next one as one finishes
• #26: draw card walls to show the activities that happen to the work rather than specific functions or job descriptions.The first school of thought says do not try to second-guess the location of bottleneck or the source of variability that will require a buffer. Rather, implement the system and wait for the bottleneck to reveal itself, then make changes to introduce a buffer. A variant on this suggests that WIP limits should be set