I don't know it, but it seems very different to me. And complex.
-Dormouse
It's not. It's just another variation on Kanban. The difference is Kanban is continuous where Scrum is iterative. There are complications you can add to it (same with Kanban), but at its root it is simple.
When I first started on my project for my world, I decided on an iteration length (2 weeks). I found high level things I wanted to get accomplished. I prioritized them, then broke them down into stories and pointed them by seeming effort required. Then I looked at what I could get accomplished in two weeks, going in priority order.
At the end of two weeks, I looked at what I'd done and delivered, and how many points it was. That helped me to see what I could get done in an iteration. Rinse and repeat, loading the backlog with things that I come up against as I went along. It helps me to plan and reach deadlines, but be agile in how I do it.
Given, I do it at work, so it's not a stretch. But I also have done Kanban at work, and it's not a lot different other than instead of iterations, you have WIP limits based on the size of the stories rather than a bucket to fill every iteration.
Kanban is generally used for support work, where Scrum is used for Greenfield development, but either can be used for either.
A good video on using it to develop worlds:
Recent Posts
Thanks for that!
