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.

1. Scrum & Kanban – Getting
the Most From Each
@MichaelSahota

2. About Michael
STRATEGIC
PLAY®
!

3. The Big Picture
@MichaelSahota

4. Agile processes come in different
flavours
Lean
Agile
(XP)Extreme
Programming
Crystal
Clear
RUP
IID
Scrum, BUT…
Kanban
Scrum

5. 2013 State of Scrum Report

6. Prescriptive vs Adaptive
processes
More prescriptive More adaptive
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
Do not develop an attachment
to any one weapon
or any one school of fighting
Miyamoto Musashi
17th century
samurai
• 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

7. Agile/Scrum Process
@MichaelSahota
Framework

9. Kanban Toolkit
@MichaelSahota

10. Kanban Toolkit: Evolve Your Process
1. Visualize Work
2. Add Metrics
3. Make Improvements

11. Visualize Work

12. Visualize Work Across Specializations

13. Establish WIP Limits

14. One day in Kanban land
Henrik Kniberg http://blog.crisp.se/author/henrikkniberg

15. Scenario 1 – one piece flow
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
B
C
A
D
E
G
F
H I
J L
M K
Henrik Kniberg 15

16. Scenario 1 – one piece flow
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
A
C B
D
E
G
F
H I
J L
M K
Henrik Kniberg 16

17. Scenario 1 – one piece flow
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
C B
G
Henrik Kniberg 17
A
D
E
F
H I
J L
M K

18. Scenario 1 – one piece flow
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
C A
D
G
Henrik Kniberg 18
B
E
F
H I
J L
M K

19. Scenario 1 – one piece flow.
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
Henrik Kniberg 19
C A
B
D
E
F
H I
J L
M K

20. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
B
C
A
D
PO
E
G
F
H I
J L
M K
Henrik Kniberg 20

21. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
A
PO
C B
D
E
G
F
H I
J L
M K
Henrik Kniberg 21

22. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
C A
D
G
Henrik Kniberg 22
B
E
F
H I
J L
M K
PO

23. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
Henrik Kniberg 23
C A
B
D
E
F
H I
J L
M K
PO

24. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
PO
Henrik Kniberg 24
C A
B
D
F
H I
J L
M K
!?
E

25. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
Henrik Kniberg 25
A
B
C
D
F E
H I
J L
M K
!?
PO

26. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
Henrik Kniberg 26
A
B
C
D
F E
H I
J L
M K
PO

27. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
Henrik Kniberg 27
A
B
D
F E
H I
J L
M K
C
PO

28. Scenario 2 – Deployment problem
Next Dev
Backlog 3 2 In production :o)
Done
Ongoing
G
Henrik Kniberg 28
D A
B
E F
H I
J L
M K
C
PO

29. Kanban Board

30. Collect key metrics on card

31. Scientific Kanban

32. Agile Kanban

33. What Fits with Kanban?

34. Culture and Why it Matters
@MichaelSahota

35. 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/

36. Copyright VersionOne 2010

38. http://www.flickr.com/photos/tza/3214197147

39. Most Value Comes from Mindset/Culture, not Practices
~20%

40. Benefit

41. ~3X

42. Benefit

43.
• Ability

44. to

45. manage

46. changing

47.
priorities

48.
• Improved

49. Visibility

50.
• Increased

51. Productivity

52.
• Improved

53. Quality

54.
• Reduced

55. Risk

56.
• Customer

57. Delight

58.
• Joy

59. at

60. work

61.
• Engagement

62.
• Innovation,

63. Creativity

64.
• Continuous

65. Learning

67. 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.

68. Option 1b: Stealth Agile

69. Option 1c: Use Kanban Toolkit to Start
Evolving Your Process Practices
1. Visualize Work
2. Add Metrics
3. Make Improvements

71. Option 2: Evolve Organizational Culture
“75% of a company’s
management is honestly
convinced that business as
usual is totally unacceptable.”
- John Kotter

73. Scrum
• Throw out your existing process
• Start with Scrum Framework
• Add in elements needed to fit your
environment (e.g. UX, Regulatory)

75. Creating A Culture Bubble

77. What is a better Question
than: Scrum vs. Kanban?

79. @MichaelSahota
Questions?

80. Do you….
Feel stuck in an Agile
Transformation?
Dream of a better place for your
people to work?
Want to love what you do?

81. If you want …
The Expert in
Agile Culture
to
Help You Grow Your
Organization
Call me.

82. “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

83. Contact Michael
Michael
Sahota
Phone:
416.999.3297
Email:
michael.sahota@agilitrix.com
Sign
up
for
my
newsleCer
at:
hCp://agilitrix.com