Embed Size (px)
Citation preview
Practical example of Scrum and Kanban use
in the same project
VS
May 30, 2015
• Developer, Project Manager, Product Manager, Game Producer, Managing Director
• Agile Enthusiast
• Traveler
• facebook.com/victor.v.bogomolov
• linkedin.com/in/vbogomolov
• appturn.com
Victor Bogomolov
Hands up...
Controversial point? Know a better solution?
Let’s have a discussion!
Consider a story through your own experience!
Doing right Scrum and right Kanban is the key!
Processes are not everything!
Use engineering practices to be successful!
Disclaimer
Free-to-play MMORPG for iOS
2+ years2 teams: 10 and 5
members
Let the adventure begin!
Phase 1: Project Kick-off and the first demo
Cross-functional team
Clear backlogClear target date for the release
New team members not familiar with Agile/Lean principles
Cross-functional team
Clear backlog
Clear target date for the release
New team members not familiar with Agile/Lean principles
Solution
Project Kick-off and the first demo
Phase 2: Incorporating feedback and researching
Considering feedback to implement
Creating new Game Design
Document
No backlog ready
R&D: work preceding main development
No backlog ready
Considering feedback to implement
Creating new Game Design
Document
R&D
work preceding main development
Incorporating feedback and research
Solution
Phase 3: Main Development
Product Development
Constraints make difference
Stories split on sprints as mini-goals
Positive stress on commitment
“Relaxation” between sprints
Productivity
Stories split into sub-tasks and estimated well
Estimation as a way to know what we need to do
Predictability
Product development
ProductivityConstraints make differenceStories split on sprints as mini-goalsPositive stress on commitment“Relaxation” between sprints
PredictabilityStories split into sub-tasks and estimated wellEstimation as a way to know what we need to do
Main development
Solution
Phase 4: Direction Change
No backlog ready
Changing game concept
Updating the Game Design Document
Tasks with neither visual output nor gameplay value
Technical development
No backlog ready
Changing game concept
Updating the Game Design Document
Technical development
Tasks with neither visual output nor gameplay value
Direction change
Solution
Phase 5: Main Development 2.0
Product development
Productivity: Proven statistically
Predictability
Product development
Productivity
Proven statistically
Predictability
Main development 2.0
Solution
Phase 6: Budget Cut
Estimations don't change plans
“Kanban & Scrum: Making the most of both” Henrik Kniberg and Mattias Skarin ©
Valuable features don't fit one sprint
Estimations don't change plans
Valuable features don't fit one sprint
Budget cut
Solution
Phase 7: Bugfix!!!
Bug fixing stage
Bugs are hard to estimate
Bug fixing stage
Hard to estimate
Bugfix!!!
Solution
Phase 8: The next-best-action strategy
Event based releases
Minimal marketable feature set (MMFs)
High responsiveness
Ability to change priorities on the fly
Event based releases
Minimal marketable feature set (MMFS)
High responsiveness
Ability to change priorities on the fly
The next-best-action strategy
Solution
Phase 9: Live Operations
Support project
No need to estimate
Unpredictable incoming flow of issues
Team of specialists
Support project
No need to estimate
Unpredictable incoming flow of issues
Team of specialists
Tools engineer
Operations engineer
Live operations
Solution
So, where we’ve arrived...
+
Scrum-ban… or not?
Scrum Kanban
Cross-functional team Required Optional
Team of specialists Prohibited Allowed
Product development
Support project
Bugfixing stage
No backlog ready
Estimations don’t change plans
No need to estimate
Ability to release anytime
Ability to change priorities on the fly (responsiveness)
Productivity and predictability
Use of Scrum Vs. Kanban
Similarities• Both are Lean and Agile.
• Both use pull scheduling.
• Both limit WIP.
• Both use transparency to drive process improvement.
• Both focus on delivering releasable software early and often.
• Both are based on self-organizing teams.
• Both require breaking the work into pieces.
• In both, the release plan is continuously optimized based on empirical data (velocity / lead time)
“Kanban & Scrum: Making the most of both” Henrik Kniberg and Mattias Skarin ©
DifferencesScrum Kanban
Timeboxed iterations prescribed. Timeboxed iterations optional. Can have separate cadences for planning, release, and process improvement. Can be event-driven instead of timeboxed.
Team commits to a specific amount of work for this iteration.
Commitment optional.
Uses Velocity as default metric for planning and process improvement.
Uses Lead time as default metric for planning and process improvement.
Cross-functional teams prescribed. Cross-functional teams optional. Specialist teams allowed.
Items must be broken down so they can be completed within 1 sprint
No particular item size is prescribed.
Burndown chart prescribed. No particular type of diagram is prescribed.
WIP limited indirectly (per sprint) WIP limited directly (per workflow state)
Estimations prescribed Estimations optional
Cannot add items to ongoing iteration Can add new items whenever capacity is available.
A sprint backlog is owned by one specific team. A kanban board may be shared by multiple teams or individuals.
Prescribes 3 roles (PO/SM/Team) Doesn’t prescribe any roles
A Scrum board is reset between each sprint. A kanban board is persistent.
Prescribes a prioritized product backlog Prioritization is optional.
Scrum Vs. Kanban Summary
1. What is Kanban? http://www.everydaykanban.com/what-is-kanban/
2. “Priming Kanban” Jesper Boeg http://www.infoq.com/minibooks/priming-kanban-jesper-boeg
3. The Scrum Guide™ http://www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf
4. What is Scrumban? http://www.solutionsiq.com/what-is-scrumban/
5. Kanban vs. Scrum – How to Choose? http://www.agilevelocity.com/kanban-vs-scrum-how-to-choose/
6. “Kanban & Scrum: Making the most of both” Henrik Kniberg and Mattias Skarin http://www.infoq.com/minibooks/kanban-scrum-minibook
7. Kanban kick-start https://www.crisp.se/wp-content/uploads/2012/07/Kanban-kick-start-v2.pdf
Useful links
Experiment!
