I'm trying to use Scrumban in our org., my concern is, if there is no sprint planning and we pick up Tasks as they come our way, then what is the use of a sprint?
I fail to understand the concept of Scrum in Scrumban.
I've prepared below table to understand the difference between Scrum, Scrumban, Kanban & Kanplan, to identify what to choose for our organization.
I see we best fit in Scrum & Scrumban, however, i fail to understand how Scrumban Functions without committing what will we deliver.
Kanban and Scrum are compatible. However, not every aspect of either survives intact in a "pure" implementation of Scrumban.
A sprint forecast is not necessary when considering the total WIP and time to develop the different sizes.
For instance, if Team A has a total WIP of 11 (3 in refinement, 3 in dev, 3 in QA, 2 in deployment) then the expectation of delivery is 11 stories if they are all the same size.
Real world, you would need to do some math based on story size and development team estimates :)
There are some good articles about building a forecast out there:
http://scrumbanrevolution.com/articles/planning-with-littles-law/
http://www.scrumban.io/game-help/forecasting-with-takt-time/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.