Tech Talk: Agile 101: What are Your Teams Working On? Making Work Visible with Kanban and Scrum
2 likes968 views
This document discusses how teams can make their work visible using Kanban and Scrum. It provides an overview of Kanban and Scrum, comparing their iterative and flow-based approaches. Both frameworks focus on delivering working software frequently through limiting work-in-progress, transparency, and empirical process improvement. The document also describes how teams can coordinate using techniques like Scrum of Scrums to connect execution to organizational strategy across multiple teams.
Tech Talk: Agile 101: What are Your Teams Working On? Making Work Visible with Kanban and Scrum
- 1. World® ’16 What Are Your Teams Working On? Making Work Visible With Kanban and Scrum Skip Angel – Transformation Consultant Services Excellence – CA Technologies Val Zolyak – Principal Product Manager – CA Technologies AMT101T AGILE MANAGEMENT
- 2. 2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD © 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA. For Informational Purposes Only Terms of this Presentation
- 11. 11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Iterative Cadences Target Iteration time boxes release release plan plan planplan plan
- 14. 14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Flow Cadences Target Mixed Cadences plan plan plan release release retro retro retro retro
- 15. 15 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Pull Work Across the Board READY B C D DONE 2 4 X 5 2
- 16. 16 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Connect Execution to Strategy Initiative Feature Feature Feature Feature Feature Story Story Story T T T Story Story Story T T T Story Story Story T T T Story Story Story T T T Story Story Story T T T
- 17. 17 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Multiplying and Coordinating I-2 I-3 I-4I-1 Scrum of Scrums Scrum of Scrums Scrum of Scrums Scrum of Scrums Mid-Range Planning PO Council
- 18. 18 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Time-Boxed IterationsContinuous Flow ScrumKanban VelocityLead Time Team CommitmentLimit WIP Burndown ChartsCumulative Flow Diagram Scope of WorkQuality of Service Scale Teams 5-9 PeopleTeams have no limit 3 Roles, 3 Ceremonies, 3 Artifacts No prescriptions Pull Scheduling Transparency of Work Continuous Value Delivery Incremental and Evolutionary Principle Driven
- 19. 19 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Stay connected at communities.ca.com Thank you.
- 20. 20 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Scrum VS Kanban SCRUM KANBAN Focus on time-boxed iterations Focus on continuous flow Velocity (work done per iteration) Lead time (time to delivery) Iteration commitment Limiting Work in Progress (WIP) Burn-down Continuous Flow Diagram Scope of work in iteration Quality of service Scales with teams of teams Scales larger within team 3 roles, 3 documents, 3 meetings No prescriptions
- 21. 21 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Scrum AND Kanban ▪ Both are Lean and Agile ▪ Both use pull scheduling ▪ Both Limit WIP ▪ Both use transparency to drive process improvement ▪ Both focus on delivering releasable software early and often ▪ Both are based on self-organizing teams ▪ Both require breaking work into pieces ▪ In both, the release plan is continuously optimized based on empirical data (velocity/throughput)