This document discusses synchronizing multiple Scrum teams using Kanban principles. It begins with an overview of Scrum and problems with multi-team coordination. It then provides a overview of Kanban and key concepts like one-piece flow and limiting work-in-progress. The document applies these Kanban concepts to Scrum by removing iterations and instead using completed stories as synchronization points between teams. It advocates for decoupling Scrum activities from iterations to allow continuous work and integration.

1. Scrum & Kanban Like Chocolate and Peanut Butter

2. Synchronizing Multiple Scrum Teams

3. OverviewWhy bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

4. Who is “The Customer?”Market /CustomersBusiness UnitSoftware Development

5. Who is “The Customer?”Market /CustomersYour offering

6. Return on InvestmentReturnValueROI =InvestmentSoftware

7. The Time Value of MoneyABDCABCDCostValue

8. The Time Value of MoneyLearning also has valueValueABDCTimeInvestedhere

9. Providing Value as Fast as PossibleTeam in Kiev$Customers in Kiev

10. Software Development NirvanaContinuous flow of Working SoftwareFrequent communicationProblems found and solved right awayGoing as fast as possibleDelivering as small an increment as possibleProviding as much value as possibleWhat do we all do that is like this today?

11. The Lean Startup Model

12. Why bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

13. Bird’s Eye View of ScrumCustomers

14. Why bother?Bird’s eye view of ScrumProblems with ScrumBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

15. Product ManagementCustomers

16. IntProduct ManagementCustomers

17. IntProduct ManagementCustomers

18. Problems With Multi-Team SynchronizationCan’t say you are “shippable” if work of all teams is not integratedHardening/stabilization iterations“QA iterations” offset from “Dev iterations”Integration iterationsVisibility into problems is clearest at end of iterationResolution may not come until for multiple iterationsElisabeth says:“No Stabilization sprints!!”

19. Why bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

20. Kanbantodowipcodedtesteddonebacklog53226 – User wants to undo a depot operation3146 – User wants to replicate adepot83216 – User wants to remove a depot3247 – User wants to combine depots54246 – User wantsto unhide a depot23241 – User wantsto hide a depot23249 – User wants to copy a depot3513246 – User wantsa list of depots33244 – User wants to remove areplica83256 – User wants to rename a depot13236 – User wants to split a depot1) Visual system of managing work2) Limited work in progress3) Work is pulled through the system

21. Kanban in ActionIntCustomers

22. Whole product touch point after every story

23. Working software after ever story is completeIntProduct ManagementCustomersUse Done Stories As Sync Points

24. Why bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

25. What’s in a User Story53226 – User wantsto undo a depot operation

26. Features of All Shapes and SizesSDSpecifyDesignCodeIntegrateDocumentWrite testsTestCIWTDGradient or rhythm?

27. One Piece FlowDo you remember me?53226 – User wants to undo a depot operationIWTDSCWithin an IterationD

28. One Piece FlowIWTWTDIWTWTIWTWTIDSCDSCIDSCDDSCIDSCDSCIDSCIDSCDSCIDSCIDWTDDDDDWithin an IterationWTDWTDWT

29. Activity vs Achievement

30. One Piece FlowWDSCITDWDSCITDWithin an Iteration

31. One Piece FlowWWDSCITDSCITDDWWWWWWWDSCITDSCITDSCITDSCITDSCITDSCITDSCITDDDDDDDWDSCITDWithin an Iteration

32. One Piece Flow

33. Why bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

34. Taskboard/Limited WIP/Pulltodowipcodedtesteddone53226 – User wants to undo a depot operation3146 – User wants to replicate adepot83216 – User wants to remove a depot3246 – User wantsto create a depot53246 – User wants to combine depots53247 – User wants to combine depots54246 – User wantsto unhide a depot23241 – User wantsto hide a depot23249 – User wants to copy a depot3513246 – User wantsa list of depots33256 – User wants to rename a depot13236 – User wants to split a depot

35. wipcodedtesteddonetodo3241 – User wants to take a survey3244 – Surveyor wants to removea question133246 – Surveyor wants to create a true/false question23247 – Surveyor wants to add a freeform question33242 – Surveyor wants to browsesurvey results533245 – Surveyor wants to create a multiple choice question33243 – Surveyor wants to add anew question

36. wipcodedtesteddonetodo3241 – User wants to take a survey3244 – Surveyor wants to removea question133246 – Surveyor wants to create a true/false question23242 – Surveyor wants to browsesurvey results533247 – Surveyor wants to add a freeform question33245 – Surveyor wants to create a multiple choice question33243 – Surveyor wants to add anew question

37. wipcodedtesteddonetodo3241 – User wants to take a survey3244 – Surveyor wants to removea question133246 – Surveyor wants to create a true/false question23242 – Surveyor wants to browsesurvey results533247 – Surveyor wants to add a freeform question33245 – Surveyor wants to create a multiple choice question33243 – Surveyor wants to add anew question

38. wipcodedtesteddonetodo3241 – User wants to take a survey3244 – Surveyor wants to removea question133246 – Surveyor wants to create a true/false question23247 – Surveyor wants to add a freeform question33242 – Surveyor wants to browsesurvey results533245 – Surveyor wants to create a multiple choice question33243 – Surveyor wants to add anew question

39. wipcodedtesteddonetodo3241 – User wants to take a survey3244 – Surveyor wants to removea question133246 – Surveyor wants to create a true/false question23247 – Surveyor wants to add a freeform question33242 – Surveyor wants to browsesurvey results533245 – Surveyor wants to create a multiple choice question33243 – Surveyor wants to add anew question

40. wipcodedtesteddonetodo3241 – User wants to take a survey3244 – Surveyor wants to removea question133246 – Surveyor wants to create a true/false question23247 – Surveyor wants to add a freeform question33242 – Surveyor wants to browsesurvey results533245 – Surveyor wants to create a multiple choice question33243 – Surveyor wants to add anew question

41. Why bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

42. Scrum Activities Linked to IterationsDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories

43. Decoupling4 week iterationsDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

44. DecouplingDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

45. Stop!!DoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose storiesDecoupling3456Iterations

46. DecouplingDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

47. DecouplingDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

48. DecouplingDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

49. DecouplingDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

50. DecouplingDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose stories3456Iterations

51. Trailing 4 Week Burnup4 WeekBurnup2015Story Points105010/410/210/910/1110/1110/1510/1710/1910/2310/25Trailing 4 weeks

52. Calculating VelocityPer iterationIteration Velocity4030Story Points20100135791113151719IterationsTrailing 4 weeks4 Week Velocity4030Story Points20100135791113151719Iterations

53. Decoupling CommitmentOr else what?New Scrum Guide replaces commitment with forecastScrum CommitmentTeam will get all committed stories to ‘done’Everybody else will leave the team aloneTrust is the flip side of commitmentTrust is a two way street and requires flexibilityHandling the unexpected requires negotiation

54. Scrum Without IterationsDoneRetrospectiveIteration ReviewBacklog groomingStory estimationChoose storiesTrailing 4 week burnupTrailing 4 week velocityTrust & negotiation

55. Why bother?Bird’s eye view of ScrumProblems with multi-Scrum-team coordinationBird’s eye view of KanbanOne-piece-flow (aka small batch size)Applying Kanban basics to ScrumMoving away from iterationsSynchronized Scrum Teams

56. IntProduct ManagementCustomersMulti-Stage Continuous Integration

57. IntIntIntProduct ManagementCustomersMulti-Stage Continuous Integration

58. Product ManagementCustomersIndividuals and Interactions

59. Product ManagementCustomersAgile Project Management

60. WebMobileIntDBIntIntServerProduct ManagementCustomersSCM (Version Control)

61. WebMobileIntDBContinuous IntegrationIntIntServerProduct ManagementCustomers

62. Whole product touch point after every story

63. Working software after ever story is complete

64. Scales upIntIntIntProduct ManagementCustomersContinuous Delivery$

65. You want what!?Why can’t we finish this?Why won’t this integrate?IntWhy is this unshippable?What does that mean?IntIntProduct ManagementCustomersContinuous Touch Points