hkg15-904: scrum and kanban 101
TRANSCRIPT
The Agile Manifesto
Processes and Tools
Responding to Change
Contract NegotiationCustomer Collaboration
Comprehensive DocumentationWorking Software
Following a Plan
Individuals and Interactions
Intro to Scrum
What is Scrum?“A lightweight adaptive framework for managing complex development projects” ● Roles● Events● Artifacts● Simple set of rules
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.
KanbanWhat 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.
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
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)
Comparison of approachesAttribute 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
Comparison of approachesAttribute Scrum KanbanIncrements ● 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