Scrum vs Kanban
Transcript of Scrum vs Kanban
Blackvard Management Consulting
SCRUM vs. KANBAN
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
Blackvard Management Consultants
www.blackvard.comCopyright © Blackvard Management Consulting – All rights reserved
Erin Lett is the Operations Manager for BlackvardManagement Consulting. She holds a Bachelor’s Degree from Stetson University in Communications and has been working in the SAP, eLearning, and Software Development industries for the past 6 years.
For further information please visit:
www.blackvard.com
Copyright © Blackvard Management Consulting- All rights reserved www.blackvard.com
Your Host
Erin Lett
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
Agenda
What Will Be Covered:
1. Waterfall Development
2. SCRUM In A Nutshell
3. KANBAN In A Nutshell
4. SCRUM vs KANBAN
5. Advantages Of Both
6. Which Do We Use?
7. Q&A Session
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
Waterfall Development is a sequential design used in software development.
Progress is viewed as steadily flowing downward through phases
Originated in manufacturing & construction industries
Waterfall Development
Requirements
Design
Implementation
Verification
Maintenance
Product Requirements Document
Software Architecture
Software
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
One phase must be completed before moving on to the next phase.
Rarely re-visit a phase once it has been completed
High risk – accuracy is critical the first time around
Changes after the fact are often not possible
More costly & less efficient than Agile approaches
Waterfall Development
Value is realized at end of project (deployment).
End of project testing leaves room for unresolved issues
Stakeholder requirements & needs could have changed
Heavily reliant on planning & project managers
SCRUM & KANBAN came about due to skepticism in regards
to how to predict w/ waterfall across long periods of time.
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM In A Nutshell
SCRUM is an Agile framework used for completing complex projects.
Originally designed for software development projects.
Works successfully for any complex/innovative project
Emphasizes team collaboration & provides a minimal set of rules.
Allows for requirements to be prioritized & changed.
Gives team the power to commit to requirements per capability.
Product Backlog
Sprint Backlog
Sprint
2 – 4 Weeks
24 Hours Deliverables
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM In A Nutshell
SCRUM divides organization into small, cross-
functional & self-organizing teams.
Divide tasks into a list of small & concrete deliverables.
Arrange list by priority & estimate the relative effort for each item.
Divide time into short fixed-length iterations.
Potentially shippable code demonstrated after each iteration.
Optimize the release plan.
Update priorities; collaborating w/ customer or shareholders, based on
insight gained by inspecting the release after each iteration
Optimize the process via feedback.
Hold retrospect after each iteration
Jan May
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
KANBAN In A Nutshell
KANBAN is a technique for managing software development
processes in a highly efficient way.
Toyota’s ‘just-in-time” (JIT) production system
Limit work in progress (WIP)
Limit how much unfinished work is in progress & reduce
time it takes an item to travel through KANBAN system
Focus on Flow
Uses WIP limits & team-driven policies
Continuously Improve
Tracks effectiveness, quality, throughput, lead times, etc.
Visualize the workflow
Divide tasks into pieces, write items down & put on task board
Use columns to illustrate where each task is in workflow
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM & KANBAN As Process Tools
SCRUM & KANBAN are both process tools.
Used to accomplish a task or purpose
SCRUM – more prescriptive (more rules to follow)
KANBAN – more adaptive (fewer rules to follow)
Which is better, SCRUM or KANBAN?
The answer truly depends on your context
Knife vs fork vs chopstick
Neither one is perfect or complete.
One alone won’t depict every task/project requirement
Provide certain constraints/guidelines
Value found in tools that limit options
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
Roles of SCRUM & KANBAN
Product Owner defines & communicates product requirements.
Represents the stakeholders & voice of customer
Prioritizes & empathizes w/ team members & stakeholders
Development Team delivers Potentially Shippable Increments (PSIs).
3 – 9 individuals w/ cross-functional skills
Analyze/design/develop/test/document
SCRUM Master facilitates the SCRUM.
Removes product & deliverables impediments
Buffer between team & distractions; enforces SCRUM rules
KANBAN does not prescribe roles.
If desired, roles can be included
When adding roles, ensure value & lack of conflict with other process elements
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM vs KANBAN: Fixed Timeboxes
SCRUM - Narrows predictions to timeboxed iterations.
Choose length, keep iterations the same to establish cadence
Fixed timeboxes – 2-4 weeks in length; bookended by sprint meetings
KANBAN – Timeboxes are not prescribed.
No incremental planning (sprint meetings, etc.)
Timeboxes & increments can be included if desired
Beginning of iteration
Iteration plan is created
During iteration
Team focuses on completing task items
End of iteration
Team demonstrates working code (potentially shippable)
Retrospective – discuss & improve process
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM vs KANBAN: Tasks & Estimates
SCRUM - Team determines Tasking & Estimating during planning meetings.
How much work they can complete in a timebox to deliver an increment
KANBAN - There are no Task Estimates required.
The team simply takes the next item and begins working on it
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM vs KANBAN: Tracking
SCRUM – Tracks Velocity
How much work tends to get done over time from increment to
increment; timebox to timebox
Intended to help teams get better at their commitment to what
they can achieve within a timebox
KANBAN – Tracks Flow
Does not track velocity, but rather holds the notion of tracking: Queues: Waiting for service to begin on an item
WIP (Work In Progress): How many things are currently being worked on
Cycle Time: The moment work began on an item & how long it takes to be completely done
SCRUM & KANBAN limit Work in Progress (WIP) in different ways.
Cycle Time
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM vs KANBAN: Process Owners
SCRUM – SCRUM Master owns process
Notion of how process works is given to the Scrum Master
to help inform the team of details of defined process
KANBAN – Team owns process
No fixed defined process
Team takes whatever process is at hand &
gives measurements: Queues/ WIP/ Cycle Times
Team determines how to continually
improve the process
Recipe to
improve
capability
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
Advantages of SCRUM vs KANBAN
Advantages of SCRUM
Transparency
Improved credibility w/ clients
High product quality
Product stability
Team reaches sustainable pace
Allows client to change priorities & requirements
Advantages of KANBAN
Flexibility
Focus on continuous delivery
Increased productivity & quality
Increased efficiency
Team has ability to focus
Reduction of wasted work & time
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
SCRUM or KANBAN?
Should we use SCRUM or KANBAN?
Ask which aspects of SCRUM & KANBAN can be used to
effectively develop products & services.
Decision should be made by development & product teams.
Recently, combinations of both frameworks & best practices have been used.
Easy & worthwhile for teams to explore both options.
Copyright © Blackvard Management Consulting – All rights reserved www.blackvard.com
Have Additional Questions?
Want To Set Up A Consultation?
Email: [email protected]
Questions & Answers