620 likes | 735 Views
Scrum & Kanban Like Chocolate and Peanut Butter. About Damon Poole. Founder and CTO of AccuRev, a leading provider of Process Agnostic Software Development Tools Creator of multiple Jolt-award winning products
E N D
About Damon Poole • Founder and CTO of AccuRev, a leading provider of Process Agnostic Software Development Tools • Creator of multiple Jolt-award winning products • 20 years of process improvement leadership ranging from small co-located teams to 10,000-person global development shops. • Past President of Agile New England • Co-founder of “Agile Immersion” • Author of “DIY Agile” DIY Agile
Session Description “As you adopt Scrum across your enterprise, you will find that synchronizing the work of interdependent Scrum teams is a challenge. Kanban has a number of principles and practices that can aid this synchronization and thus smooth out your adoption. This session will introduce Kanban from a Scrum perspective, show how the Lean practice of “One Piece Flow” is the key to both, and get into the nuts and bolts of specific practices and concepts from Kanban that can be adopted by an existing multi-team Scrum program.”
Overview • Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
Who is “The Customer?” Market/Customers Business Unit Software Development
Who is “The Customer?” Market/Customers Your offering
Return on Investment Return Value ROI = Investment Software
The Time Value of Money A B D C A B C D Cost Value
The Time Value of Money Learning also has value Value A B D C Time Investedhere
Providing Value as Fast as Possible Team $ Customers
Software Development Nirvana • Continuous flow of Working Software • Providing as much value as possible • Going as fast as possible • Delivering as small an increment as possible • Frequent communication • Problems found and solved right away • What do we all do that is like this today?
Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
Scrum todo wip coded tested done 3246 – User wants to remove a depot 1 5 5 3246 – User wantsto unhide a depot 3246 – User wantsa list of depots 3246 – User wants to combine depots 3246 – User wants to copy a depot 3246 – User wantsto create a depot 3246 – User wants to rename a depot 3246 – User wantsto hide a depot 2 3 3 5 1 2 3246 – User wants to split a depot
Scrum todo wip coded tested done 3246 – User wants to remove a depot 5 3246 – User wantsto unhide a depot 3246 – User wantsa list of depots 3246 – User wantsto hide a depot 3246 – User wantsto create a depot 3246 – User wants to rename a depot 3246 – User wants to copy a depot 3246 – User wants to combine depots 1 5 2 3 3 1 2 5 3246 – User wants to split a depot
Scrum todo wip coded tested done 3246 – User wants to remove a depot 3246 – User wantsto unhide a depot 3246 – User wants to rename a depot 3246 – User wantsa list of depots 3246 – User wants to combine depots 3246 – User wants to copy a depot 3246 – User wantsto create a depot 3246 – User wantsto hide a depot 2 2 3 5 3 5 1 1 5 3246 – User wants to split a depot
Product Management Customers
Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
Int Product Management Customers
Int Product Management Customers
Problems With Multi-Team Synchronization • Can’t say you are “shippable” if work of all teams is not integrated • Integration sprints • Hardening sprints • QA Sprints • Visibility into problems is clearest at end of iteration • Resolution may not come until the next iteration
Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
Kanban backlog todo wip coded tested done 5 3226 – User wants to undo a depot operation 3146 – User wants to replicate adepot 8 3216 – User wants to remove a depot 4246 – User wantsto unhide a depot 3246 – User wantsa list of depots 3241 – User wantsto hide a depot 3249 – User wants to copy a depot 3247 – User wants to combine depots 3256 – User wants to rename a depot 3244 – User wants to remove areplica 8 5 1 3 2 2 5 3 1 3236 – User wants to split a depot 1) Visual system of managing work 2) Limited work in progress 3) Work is pulled through the system
What Kanban Can Borrow From Scrum • Backlog • Product owner • Self-organization • Co-location • Cross-functionality • Sprint review
Kanban in Action Int Customers
Use Done Stories As Sync Points • Whole product touch point after every story • Working software after ever story is complete Int Product Management Customers
Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
What’s in a User Story 5 3226 – User wantsto undo a depot operation
Features of All Shapes and Sizes S D Specify Design Code Integrate Document Write tests Test C I W T D
One Piece Flow 5 3226 – User wants to undo a depot operation I W T S D C Within an Iteration D
One Piece Flow D W I I W I W T T T W W W T T T I S S S S S S S S S D D D D D D S D D D D C C C C C C C I C C C I I I I I D W T D D D D D D Within an Iteration W W T W T D T D
One Piece Flow W S D C I T D W S D C I T D Within an Iteration
One Piece Flow W W S S D D C C I I T T D D W W W W W W W S S S S S S D D D D D D C C C C C C I I I I I I T T T T T T S D C I T D D D D D D D W S D C I T D Within an Iteration
Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
Taskboard/Limited WIP/Pull todo wip coded tested done 5 3226 – User wants to undo a depot operation 3146 – User wants to replicate adepot 8 3216 – User wants to remove a depot 4246 – User wantsto unhide a depot 3256 – User wants to rename a depot 3246 – User wantsto create a depot 3246 – User wants to combine depots 3241 – User wantsto hide a depot 3249 – User wants to copy a depot 3246 – User wantsa list of depots 3247 – User wants to combine depots 1 2 2 3 5 5 1 3 5 5 3236 – User wants to split a depot
wip coded tested done todo 3241 – User wants to take a survey 3246 – Surveyor wants to create a true/false question 3242 – Surveyor wants to browsesurvey results 3244 – Surveyor wants to remove a question 3247 – Surveyor wants to add a freeform question 3 2 3 5 1 3 3245 – Surveyor wants to create a multiple choice question 3 3243 – Surveyor wants to add anew question
wip coded tested done todo 3241 – User wants to take a survey 3246 – Surveyor wants to create a true/false question 3242 – Surveyor wants to browsesurvey results 3244 – Surveyor wants to remove a question 3247 – Surveyor wants to add a freeform question 3 2 5 3 1 3 3245 – Surveyor wants to create a multiple choice question 3 3243 – Surveyor wants to add anew question
wip coded tested done todo 3241 – User wants to take a survey 3246 – Surveyor wants to create a true/false question 3247 – Surveyor wants to add a freeform question 3244 – Surveyor wants to remove a question 3242 – Surveyor wants to browsesurvey results 2 5 3 3 1 3 3245 – Surveyor wants to create a multiple choice question 3 3243 – Surveyor wants to add anew question
wip coded tested done todo 3241 – User wants to take a survey 3246 – Surveyor wants to create a true/false question 3244 – Surveyor wants to remove a question 3242 – Surveyor wants to browsesurvey results 3247 – Surveyor wants to add a freeform question 2 3 5 3 1 3 3245 – Surveyor wants to create a multiple choice question 3 3243 – Surveyor wants to add anew question
wip coded tested done todo 3241 – User wants to take a survey 3246 – Surveyor wants to create a true/false question 3244 – Surveyor wants to remove a question 3242 – Surveyor wants to browsesurvey results 3247 – Surveyor wants to add a freeform question 2 3 5 3 1 3 3245 – Surveyor wants to create a multiple choice question 3 3243 – Surveyor wants to add anew question
wip coded tested done todo 3241 – User wants to take a survey 3246 – Surveyor wants to create a true/false question 3244 – Surveyor wants to remove a question 3242 – Surveyor wants to browsesurvey results 3247 – Surveyor wants to add a freeform question 2 3 5 3 1 3 3245 – Surveyor wants to create a multiple choice question 3 3243 – Surveyor wants to add anew question
Why bother? • Bird’s eye view of Scrum • Problems with multi-Scrum-team coordination • Bird’s eye view of Kanban • One-piece-flow (aka small batch size) • Applying Kanban basics to Scrum • Moving away from iterations • Synchronized Scrum Teams
Scrum Activities Linked to Iterations Done Retrospective Iteration Review Backlog grooming Story estimation Choose stories
Decoupling 4 week iterations Done Retrospective Iteration Review Backlog grooming Story estimation Choose stories 3 4 5 6 Iterations
Decoupling Done Retrospective Iteration Review Backlog grooming Story estimation Choose Stories 3 4 5 6 Iterations
Decoupling Stop!! Done Retrospective Iteration Review Backlog grooming Story estimation Choose Stories 3 4 5 6 Iterations
Decoupling Done Retrospective Iteration Review Backlog grooming Story estimation Choose Stories 3 4 5 6 Iterations
Decoupling Done Retrospective Iteration Review Backlog grooming Story estimation Choose Stories 3 4 5 6 Iterations