Scrumban Lightning talk

1,521 views

Published on

Here is the deck that I presented in my Lightning talk @ Agile Cafe

Published in: Technology, Business
1 Comment
7 Likes
Statistics
Notes
  • Great presentation, thanks! I think both Scrum and Kanban have their limitations. That's why it's so important to join them. It makes us more flexible and able to adapt to changing environment. Of course, there are some similarities between the methods, like explained for example here: http://kanbantool.com/kanban-library/scrumban/scrum-and-kanban-both-the-same-only-different but it may be valuable to notice the differences and take them both, joined together into consideration.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,521
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
63
Comments
1
Likes
7
Embeds 0
No embeds

No notes for slide
  • {}
  • Scrumban Lightning talk

    1. 1. Scrumban What? Why? How?
    2. 2. Speaker : Lalita Chandel @LalitaChnd http://www.linkedin.com/pub/lalita-chandel/25/848/271 • Certified Scrum Master. • Agilist with 8+ years of IT experience.
    3. 3. Our Customers want EVERYTHING !
    4. 4. … and with time, they discover what they really NEED
    5. 5. … and with time, they discover what they really NEED, that again CHANGES with time.
    6. 6. Software Development
    7. 7. Scrum : Pig - Chicken Game
    8. 8. Where do you fit ?   X axis - Work Spectrum Y axis - Work Environment
    9. 9. Kanban
    10. 10. Pillars of Kanban
    11. 11. It’s time to….
    12. 12. How about mixing both ?
    13. 13. Scrumban  Use Prescriptive nature ( Roles & communication ) of Scrum to be Agile.  Use Adaptive nature ( Process improvement) of Kanban to continuously improve the process.
    14. 14. When to use Scrumban ?
    15. 15. Visualizing Scrumban
    16. 16. Scrumban Board
    17. 17. Quickly look again Kanban Daily Stand-ups Scrum Metrics Yes Backlog, Current None Work, Burndown Charts Lead Time/Cycle Time Velocity Demo Not used Skill Sets Specialized Iterations Retrospective No Prioritized Immediately Not used Defined Roles None Artifacts New Work No Required Scrum-Ban Yes Current Work Lead Time/Cycle Time Optional Either Specialized or Cross-Functional Cross-Functional Yes No Prioritized at Sprint Prioritized Planning Meeting Immediately Required Optional Product Owner, Scrum Product Owner, Scrum Master, Scrum Team Master, Scrum Team
    18. 18. Nothing works without the Teamwork !!
    19. 19. Let’s use the ….. for great Agility in Software products & services.

    ×