HKG15-904: Scrum and Kanban 101 --------------------------------------------------- Speaker: Amro Hassaan Date: February 11, 2015 --------------------------------------------------- ★ Session Summary ★ An introduction to the Agile Methodologies of Scrum and Kanban frameworks. First a review of each framework and then a comparison of each. -------------------------------------------------- ★ Resources ★ Pathable: https://hkg15.pathable.com/meetings/250819 Video: https://www.youtube.com/watch?v=o0w8AXW832c Etherpad: N/A --------------------------------------------------- ★ Event Details ★ Linaro Connect Hong Kong 2015 - #HKG15 February 9-13th, 2015 Regal Airport Hotel Hong Kong Airport --------------------------------------------------- http://www.linaro.org http://connect.linaro.org

1. Amro Hassaan, Tools Analyst, PMO.
Scrum and Kanban 101

2. What is Waterfall?
Waterfall

3. The Agile Processes
Scrum
Crystal
Clear
Agile Unified
Process
KanbanLean
XP

4. The Agile Manifesto
Processes and Tools
Responding to Change
Contract NegotiationCustomer Collaboration
Comprehensive DocumentationWorking Software
Following a Plan
Individuals and Interactions

5. Intro to Scrum
What is Scrum?
“A lightweight adaptive framework for managing complex
development projects”
● Roles
● Events
● Artifacts
● Simple set of rules

6. Product Owner

7. Scrum Master & Team
● A Scrum Master is a servant leader who facilitates the
development process, removes blocking issues and
ensures the team is adhering to the process.
● A Team is a self-organizing, cross-functional team that
undertakes the responsibility of delivering the work.

9. Kanban
What is Kanban?
A work management approach focused on enhancing
production flow by increasing the visibility of the workflow,
and by limiting the amount of work in progress (WIP).
● Pioneered by Taiichi Ohno (Toyota)
● Underpins “Just In Time” approach (JIT)
● Focused on speed, predictability, continuous improvement.
● Reduces “Muda” or waste, time item sits idle (not worked on).
● kan (visual) - ban (card)
● Kanban → process.
● kanban → card.

10. Properties of the Kanban method
● Visualize workflow
● Limit work in process (WIP)
● Measure and manage flow
● Make process policies explicit
● Recognize improvement opportunities
Cycle Time
Time spent working on an item from start to completely done.
Lead Time
Total time a request or an item spends in the process from start to end.
CT = work time LT = idle time + work time
Value Stream Mapping

11. Implementing Kanban
10 234
Cycle Time

14. Limiting Work In Progress/Process (WIP)
A fundamental concept in Kanban! Why?
● Reduces multi-tasking.
● Increases focus by limiting context switching.
● Improves performance (reduces Cycle time).
● Reduces the average Lead Time.
● Help identify bottlenecks.
● Increases team collaboration.
● Very experimental (you improve WIP estimation through
observing performance and adjusting)

15. Comparison of approaches
Attribute Scrum Kanban
Cadence Time box iterations Continuous Flow
Key Metrics Velocity Cycle Time
Defining
Characteristics
3 roles,
3 events,
4 artifacts
-Visualize WF
-Limit WIP
-No clearly defined roles
Key Artifact Burn-down diagram Cumulative Flow diagram
Team Scalability Hierarchy of small teams Support for larger team

16. Comparison of approaches
Attribute Scrum Kanban
Increments ● Smaller increments
● Feedback to increase ROI
● Mitigate risk
● Maximize Learning process
Retrospective At the end of each sprint Daily
Management
Inclusion
Sprint is black box and
management get visibility at the
end of the sprint
Daily visibility and inclusion
allows management to
see/understand bottlenecks and
level of scope-creep is
decreased