Saturday, March 5, 2011

Scrum Ban for Maintenance / Operations Projects

Scrum Ban for Maintenance / Operations Projects

A solution where we use all ceremonies of Scrum and Kanban to pull the work instead of Sprint Backlog

This started as when I was managing Post Release Support Project it became very difficult to use scrum end to end with daily changes in requirement priorities. Our Sprints were getting scraped frequently. This clearly showed that Scrum is not the solution then what should I do to for team that they are getting benefits of Scrum and still could manage with the changing requirements and priorities. And I could get the Solution of Scrum Ban.

Scrum Ban follows all ceremonies of Scrum. How its different is as follows:
1) Doesn’t have sprint-planning can rather have Monthly Iteration planning or Release planning.
2) Product backlog is used to pull the work where work can be stored in priority order, as Business needs. This can change daily.
3) Work in Progress monitored rather than Velocity.
4) Queue Limits gives more flexibility to pull work if floating expertise called in Maintenance projects.

change-management-scale-skill-shy

https://www.linkedin.com/pulse/change-management-scale-skill-shy-mansi-mahur?trk=portfolio_article-card_title