scrum and kanban - getting the most from each
DESCRIPTION
Scrum is the most popular Agile methodology with Kanban a growing second choice. Learn about the core parts of each one as well as how they differ so that you can find the best fit for your team or organizational context. For example, Scrum is great when you want to shake up the status quo and transform the way you work. Kanban is great when small changes are a better fit for the environment. Learn how they work and how you can use them in your environment.TRANSCRIPT
@MichaelSahota
Scrum & Kanban – Getting the Most From Each
About Michael
STRATEGIC PLAY®
!
@MichaelSahota
The Big Picture
Lean
Agile processes come in different flavours
Agile
(XP)Extreme Programming
Crystal Clear
Scrum, BUT…
RUP
IID
Kanban
Scrum
2013 State of Scrum Report
More prescriptive More adaptive
Prescriptive vs Adaptive processes
XP (13)
Scrum (9)
Kanban (3)
Do Whatever (0)
RUP (120+)
• Architecture Reviewer • Business Designer • Business-Model Reviewer • Business-Process Analyst • Capsule Designer • Change Control Manager • Code Reviewer • Configuration Manager • Course Developer • Database Designer • Deployment Manager • Design Reviewer • Designer • Graphic Artist • Implementer • Integrator • Process Engineer • Project Manager • Project Reviewer • Requirements Reviewer • Requirements Specifier • Software Architect • Stakeholder • System Administrator • System Analyst • Technical Writer • Test Analyst • Test Designer • Test Manager • Tester • Tool Specialist • User-Interface Designer • Architectural analysis • Assess Viability of architectural
proof-of-concept • Capsule design • Class design • Construct architectural proof-
of-concept • Database design • Describe distribution • Describe the run-time
architecture • Design test packages and
classes • Develop design guidelines • Develop programming
guidelines • Identify design elements • Identify design mechanisms • Incorporate design elements • Prioritize use cases • Review the architecture • Review the design • Structure the implementation
model • Subsystem design • Use-case analysis • Use-case design • Analysis model • Architectural proof-of-concept • Bill of materials • Business architecture
document • Business case • Business glossary • Business modeling guidelines • Business object model • Business rules • Business use case
• Whole team • Coding standard • TDD • Collective ownership • Customer tests • Pair programming • Refactoring • Planning game • Continuous integration • Simple design • Sustainable pace • Metaphor • Small releases
• Scrum Master • Product Owner • Team • Sprint planning
meeting • Daily Scrum • Sprint review • Product backlogt • Sprint backlog • BUrndown chart
• Visualize the workflow • Limit WIP • Measure and optimize lead
time
Miyamoto Musashi 17th century samurai
Do not develop an attachment to any one weapon or any one school of fighting
• Business use case realization • Business use-case model • Business vision • Change request • Configuration audit findings • Configuration management
plan • Data model • Deployment model • Deployment plan • Design guidelines • Design model • Development case • Development-organization
assessment • End-user support mateirla • Glossary • Implementation model • Installation artifacts • Integration build plan • Issues list • Iteration assessment • Iteration plan • Manual styleguide • Programming guidelines • Quality assurance plan • Reference architecture • Release notes • Requirements attributes • Requirements
management plan • Review record • Risk list • Risk management plan • Software architecture
document • Software development
plan • Software requirements
specification • Stakeholder requests • Status assessment • Supplementary business
specification • Supplementary specification • Target organization
assessment • Test automation architecture • Test cases • Test environment configuration • Test evaluation summary • Test guidelines • Test ideas list • Test interface specification • Test plan • Test suite • Tool guidelines • Training materials • Use case model • Use case package • Use-case modeling guidelines • Use-case realization • Use-case storyboard • User-interface guidelines • User-interface prototype • Vision • Work order • Workload analysis model
Henrik Kniberg
@MichaelSahota
Agile/Scrum Process Framework
@MichaelSahota
Kanban Toolkit
Kanban Toolkit: Evolve Your Process
1. Visualize Work 2. Add Metrics 3. Make Improvements
Visualize Work
Visualize Work Across Specializations
Establish WIP Limits
One day in Kanban land
Henrik Kniberg http://blog.crisp.se/author/henrikkniberg
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 1 – one piece flow
Henrik Kniberg 15
B C
A
D
E
F
G
H I J L
K M
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 1 – one piece flow
Henrik Kniberg 16
B C
A
D
E
F
G
H I J L
K M
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 1 – one piece flow
Henrik Kniberg 17
B C
A
D
E
F
G
H I J L
K M
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 1 – one piece flow
Henrik Kniberg 18
B C A D
E
F
G
H I J L
K M
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 1 – one piece flow.
Henrik Kniberg 19
B C A
D
E
F
G
H I J L
K M
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 20
B C
A
D
E
F
G
H I J L
K M
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 21
B C
A
D
E
F
G
H I J L
K M
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 22
B C A D
E
F
G
H I J L
K M
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 23
B C A
D
E
F
G
H I J L
K M
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 24
B C A
D F
G
H I J L
K M
!?
E
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 25
B C
A D E F
G
H I J L
K M
!? PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 26
B C
A D E F
G
H I J L
K M
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 27
B A
D E F
G
H I J L
K M
C
PO
Next Dev
Done Backlog 3
2 In production :o) Ongoing
Scenario 2 – Deployment problem
Henrik Kniberg 28
B A D
E F
G
H I J L
K M
C
PO
Kanban Board
Collect key metrics on card
Scientific Kanban
Agile Kanban
What Fits with Kanban?
@MichaelSahota
Culture and Why it Matters
Agile Fails Due to Culture
Sources: Multiple Workshops with 100’s of participants; Version One Survey http://agilitrix.com/2012/08/agile-2012-workshop-results/
Copyright VersionOne 2010
http://www.flickr.com/photos/tza/3214197147
Most Value Comes from Mindset/Culture, not Practices
~20%����������� ������������������ Benefit����������� ������������������ ~3X����������� ������������������ Benefit����������� ������������������ • Ability����������� ������������������ to����������� ������������������ manage����������� ������������������ changing����������� ������������������ priorities����������� ������������������ • Improved����������� ������������������ Visibility����������� ������������������ • Increased����������� ������������������ Productivity����������� ������������������ • Improved����������� ������������������ Quality����������� ������������������ • Reduced����������� ������������������ Risk����������� ������������������
• Customer����������� ������������������ Delight����������� ������������������ • Joy����������� ������������������ at����������� ������������������ work����������� ������������������ • Engagement����������� ������������������ • Innovation,����������� ������������������ Creativity����������� ������������������ • Continuous����������� ������������������ Learning����������� ������������������
Option 1a: Adopt Agile Practices that fit Culture
Example: Introducing automated testing to reduce regression test costs and time.
Find the practice (puzzle piece) that fits your problem.
Option 1b: Stealth Agile
Option 1c: Use Kanban Toolkit to Start Evolving Your Process & Practices
1. Visualize Work 2. Add Metrics 3. Make Improvements
Option 2: Evolve Organizational Culture
“75% of a company’s management is honestly convinced that business as usual is totally unacceptable.” - John Kotter
Scrum
• Throw out your existing process • Start with Scrum Framework • Add in elements needed to fit your
environment (e.g. UX, Regulatory)
Creating A Culture Bubble
What is a better Question than: Scrum vs. Kanban?
@MichaelSahota
Questions?
Do you…. Feel stuck in an Agile Transformation? Dream of a better place for your people to work? Want to love what you do?
The Expert in Agile Culture� to
Help You Grow Your Organization
Call me.
If you want …
“We thought we were hiring Michael to teach our staff how to 'do agile' but he taught us so much more than that. We started with an intense but stunningly effective Temenos session for the management team that was crucial to building the trust and connection we needed to truly function as a team. He facilitated a series of organizational development workshops that helped us understand and build towards a cultural and organizational context where agility can thrive and be sustained. Using a dynamic and highly engaging 'teach by modeling' style throughout, Michael helped us examine our team's values, mission and ambitions, adjust our structure and move us towards an empowered model of decision-making. When we finally rolled out Scrum and Kanban training, we were well positioned to support successful adoption. Michael is a master facilitator who applied expertise, experience, compassion and courage to navigate complex problems with us and put us on the path to transformation.”
- Soo Kim, Senior Director, Digital Operations, CBC
Contact Michael
Michael Sahota Phone: 416.999.3297 Email: [email protected] Sign up for my newsleCer at: hCp://agilitrix.com