• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
From Scrum to Scrumban
 

From Scrum to Scrumban

on

  • 3,670 views

A presentation of the evolutoi

A presentation of the evolutoi

Statistics

Views

Total Views
3,670
Views on SlideShare
1,720
Embed Views
1,950

Actions

Likes
3
Downloads
41
Comments
0

9 Embeds 1,950

http://johnpeltier.com 1840
http://www.scoop.it 41
http://scrumban.fr 28
http://www.twylah.com 17
http://plus.url.google.com 12
http://www.linkedin.com 8
http://webcache.googleusercontent.com 2
http://translate.googleusercontent.com 1
https://www.linkedin.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • How many project managers are in the room?
  • Comparison:Rituals in common: Retrospective, Demo, StandupsDifferences: Commit; Sprint Planning
  • For those of you who are not familiar with product management…KNOBThe interest in meeting deadlines is really backed by market pressures – market opportunity is often times limited by time.
  • Scrum is aniterative process of software development, characterized by a small team of people working together on individual tasks and then moving on to the next one.TIMEBOXIn scrum, work is broken up into “user stories” that compose the product backlogSome subset is estimated and brought into the individual sprint backlogThose are built and tested and made ready for productionThen the next subset is started in the following sprintThe number of “points” completed contributes to velocity.
  • Scrum ritualsSprint kickoffDaily standupSprint DemoRetrospective
  • Kanban is a pull-based system of managing work. The team works on an individual item to completion before taking on a new one. 2 keys:1) No iterations – the team simply burns through items in priority order.2) Planning of the story happens as the story is started, NOT at the beginning of the iteration.Kanban is characterized byExplicit work in progress limitsVisual workflow (frequently borrowed by scrum)Emphasis on “cycle time” to increase rate of flow
  • Retaining iterations provides structureBut still allowing for JIT elaboration upon stories
  • One of the big obvious questions…The team must already know the vision of what they’re going to build.Attention to story splitting: - leave them too large - or drill down by…….
  • In a commercial software organization, the product manager is juggling many things besides engineering.By conducting release planning and then getting to work, we have counteracted the product owner’s sporadic availability so that it is not an obstacle. Product owner is present 50% of time, always for standupsWhen the team is ready to start a new story, PO makes himself availableTeam takes responsibility for some analysis (particularly on technical stories)Scrumban doesn’t work if the team doesn’t know what it’s doing next!

From Scrum to Scrumban From Scrum to Scrumban Presentation Transcript