In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
4. Why you should hear this?
• You are doing product development
5. Why you should hear this?
• You are doing product development
• You are in a startup
6. Why you should hear this?
• You are doing product development
• You are in a startup
• Your team is less or equal to 8 people
7. Why you should hear this?
• You are doing product development
• You are in a startup
• Your team is less or equal to 8 people
• Uncertainty is a daily thing for you
8. Why you should hear this?
• You are doing product development
• You are in a startup
• Your team is less or equal to 8 people
• Uncertainty is a daily thing for you
• You have heard or practiced agile and lean
25. Product, project or
support?
Product Project Support
Assembly
line
Single
product
Do you
know the
deadline?
Estimate
No estimate,
focus on goals
Average
estimate
Features or
knowledge
?
FeaturesKnowledge
Do you
need to
know it?
Yes
No
Yes
No
Do you
prioritize by
estimate?
Yes
No
34. 3kings to rule them all
Daily meeting
Planning meeting
(on demand)
Kaizen
35. Aligned vision
Scrum Kanban Scrumban
Iterations 1-4 week sprints Continuous work Continuous work with with decoupled
planning and release
Work routines Pull principle Pull principle or late binding to resources Pull principle or late binding to resources
Scope limits Sprint limits total work amount Work in progress limits current work amount Work in progress limits current work
amount,
Buffer defines triggers for planning
Planning routines Sprint planning Release/iteration planning, demand
planning
Planning on demand for new tasks
Estimation Backlog and sprint planning Optional Average or no-estimation
Performance metrics Burndown, Velocity Cumulative flow diagram, lead time cycle
time
Average cycle time
Continuous improvement Retrospective Optional Kaizen
Meetings Sprint planning, daily scrum, sprint review,
retrospective
Kaizen Daily, on demand planning, kaizen
Roles Product owner, Scrum master, team Team leader, team Team leader, team
Team members Cross-functional team members Specialized team members Specialization or preference to tasks
Task size Should be less than 8 hours to see progress Any size Any size
New items during iteration Forbidden in most cases Allowed whenever queue allows it Allowed through buffer swap
Ownership Owned by a team Supports multiple teams ownership Supports multiple teams ownership
Board Defined/reset each sprint Persistent Persistent
Prioritization During backlog and sprint planning Optional Always open
Roles Scrum master, product owner, team Not defined, may vary Not defined, may vary
Rules Constrained process Only a few constraints, flexible process Slightly constrained process
Fit for Enterprise maturity for teams working on
product or especially project which is longer
than a year
Support and maintenance teams,
continuous product manufacturing
Startups, fast-pace projects, continuous
product manufacturing