O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Scrum-ban
mixing agile and lean
By Vidas Vasiliauskas
About me
• Product manager at Eylean board
• Started career as a developer
• 8 years in software industry
• Doing “lean st...
Why you should hear this?
Why you should hear this?
• You are doing product development
Why you should hear this?
• You are doing product development
• You are in a startup
Why you should hear this?
• You are doing product development
• You are in a startup
• Your team is less or equal to 8 peo...
Why you should hear this?
• You are doing product development
• You are in a startup
• Your team is less or equal to 8 peo...
Why you should hear this?
• You are doing product development
• You are in a startup
• Your team is less or equal to 8 peo...
Scrum vs Scrum-ban
Scrumban 101
Goals:
• Minimum delivery time
• Fully loaded team
Features:
• Event/demand driven
• Empowers team roles
• Le...
Backlog
--------
--------
--------
--------
Planning
Daily
meeting
Production
Release
Planning
trigger?
5-15% of
overall t...
Task board
To do Doing Done
Analyze
requirements
Develop project
plan
Develop project
plan
Initiate
agreement
Planning on demand
GOLDEN RULE:
Demand goes first before supply
To do Doing Done
Analyze
requirements
Define
specifications
Create design
guidelines
Initiate
agreement
Create design
docs
To do Doing Done
Analyze
requirements
Define
specifications
Create design
guidelines
Initiate
agreement
Create design
docs...
To do Doing Done
Analyze
requirements
Define
specifications
Create design
guidelines
Initiate
agreement
Create design
docs...
To do Doing Done
Analyze
requirements
Define
specifications
Create design
guidelines
Initiate
agreement
Create design
docs...
To do Doing Done
Analyze
requirements
Define
specifications
Create design
guidelines
Initiate
agreement
Create design
docs...
Less planning and concentrated release
Points done
Time
Points
Items done
Time
Tasks
Tasks done
Time
Tasks
Tasks done
Feature
freeze
Triage
Stabilization
Estimating is easy…
Product, project or
support?
Product Project Support
Assembly
line
Single
product
Do you
know the
deadline?
Estimate
No es...
Task
created
Task
started
Task
delivered
Lead time
Planning on
demand
Cycle time
4guidelines to control cycle time
1. Prefer completed task to
starting new
4guidelines to control cycle time
2. Grab second task only if the
first one is blocked
*can overcome rule 1.
4guidelines to control cycle time
3. Late resource binding
4guidelines to control cycle time
4. Avoid critical path
NO! To early binding
+STRESS
-ENERGY
-TIME
* Mind the impact
Push system Pull system
3kings to rule them all
Daily meeting
Planning meeting
(on demand)
Kaizen
Aligned vision
Scrum Kanban Scrumban
Iterations 1-4 week sprints Continuous work Continuous work with with decoupled
plann...
THANK YOU
www.aboutscrumban.com
@Vasiliauskas
vidas@eylean.com
+370 600 37066
Scrumban - applying agile and lean practices for daily uncertainty by Vidas Vasikiauskas
Próximos SlideShares
Carregando em…5
×

Scrumban - applying agile and lean practices for daily uncertainty by Vidas Vasikiauskas

2.356 visualizações

Publicada em

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.

  • Seja o primeiro a comentar

Scrumban - applying agile and lean practices for daily uncertainty by Vidas Vasikiauskas

  1. 1. Scrum-ban mixing agile and lean By Vidas Vasiliauskas
  2. 2. About me • Product manager at Eylean board • Started career as a developer • 8 years in software industry • Doing “lean startup”
  3. 3. Why you should hear this?
  4. 4. Why you should hear this? • You are doing product development
  5. 5. Why you should hear this? • You are doing product development • You are in a startup
  6. 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. 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. 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
  9. 9. Scrum vs Scrum-ban
  10. 10. Scrumban 101 Goals: • Minimum delivery time • Fully loaded team Features: • Event/demand driven • Empowers team roles • Lean like hell
  11. 11. Backlog -------- -------- -------- -------- Planning Daily meeting Production Release Planning trigger? 5-15% of overall time left until release date? Task board Task board Triage Feature freeze Stabilization Kaizen? Kaizen YES No YES No No YES
  12. 12. Task board To do Doing Done Analyze requirements Develop project plan Develop project plan Initiate agreement
  13. 13. Planning on demand GOLDEN RULE: Demand goes first before supply
  14. 14. To do Doing Done Analyze requirements Define specifications Create design guidelines Initiate agreement Create design docs
  15. 15. To do Doing Done Analyze requirements Define specifications Create design guidelines Initiate agreement Create design docs 2
  16. 16. To do Doing Done Analyze requirements Define specifications Create design guidelines Initiate agreement Create design docs Buffer Develop project plan Transfer documents 2
  17. 17. To do Doing Done Analyze requirements Define specifications Create design guidelines Initiate agreement Create design docs Buffer Develop project plan Transfer documents 22
  18. 18. To do Doing Done Analyze requirements Define specifications Create design guidelines Initiate agreement Create design docs Buffer Develop project plan Transfer documents 22 TRIGGER!!!
  19. 19. Less planning and concentrated release
  20. 20. Points done Time Points
  21. 21. Items done Time Tasks Tasks done
  22. 22. Time Tasks Tasks done Feature freeze Triage Stabilization
  23. 23. Estimating is easy…
  24. 24. 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
  25. 25. Task created Task started Task delivered Lead time Planning on demand Cycle time
  26. 26. 4guidelines to control cycle time 1. Prefer completed task to starting new
  27. 27. 4guidelines to control cycle time 2. Grab second task only if the first one is blocked *can overcome rule 1.
  28. 28. 4guidelines to control cycle time 3. Late resource binding
  29. 29. 4guidelines to control cycle time 4. Avoid critical path
  30. 30. NO! To early binding +STRESS -ENERGY -TIME
  31. 31. * Mind the impact
  32. 32. Push system Pull system
  33. 33. 3kings to rule them all Daily meeting Planning meeting (on demand) Kaizen
  34. 34. 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
  35. 35. THANK YOU www.aboutscrumban.com @Vasiliauskas vidas@eylean.com +370 600 37066

×