Please enable JavaScript.
Coggle requires JavaScript to display documents.
Scrumban - Coggle Diagram
Scrumban
Why
no "kanban process"
kanban needs process context for meaningful application
Practitioners need examples of process transformation using kanban
Scrumban is a simple story with a pratical outcome that man people can relate to
Scrumban is one of the possible stories about Lean transformation
Scrumban is more Scrum than Scrum
The New New Product Development Game
evolutionary design
evolutionary enhancement
grow software
instead of build it
Selection
Parallel
Spatial
Iteration
Serial
Temporal
we can do both
Throughput Management
Business value
lantency
manage bandwidth by policy
Kanban makes quantitative management easy
Metrics
CFD
Feature crews
Large-Scale pull scheduling system used by Microsoft Office
Cross-functional Workcell
Internaly self organized
branch by feature
quality gates
Tasks Cards
Problem with WIP
Limit
Multasking
Late binding
We limit as a team
Specialization
columns for team members
faster velocity
Rolling Wave Planning
6 weeks bucket
well defined MMF - Minimal Marketable Feature
3 months bucket
loosely-defined features
6 months bucket
broad features area
1 year bucket
strategies
goals
market forces
Referências
https://vimeo.com/88885445
scrumban: essays on kanban systems for lean software development” by corey ladas
https://en.wikipedia.org/wiki/Scrumban
Large Scale Kanban Systems
Feature Crews
MMF
Rolling Wave
planning-on-demmand
best thing to work next
games
Pull scheduling
vminimize NVA overhead
Production leveling
balance stakeholder voices
option thinkig
decision markets
make options complete for inclusion in planning portfolio
theory
Mechanism design
Auction systemms
voting systems
Organization
Workcell
serial flow
Order point
When backlog goes below a predefined threshold, planning is triggered
Production Leveling
fixed-size backlog
Minimal Marketable Feature
Incrementing funding model