Kanban or Scrum?
Ever wonder...
When does it make sense to use Scrum over Kanban?
Hey, maybe I would be better off with Kanban?
Is my methodology really working or is there something better?
So, this morning I was trying to analyze my new projects, thinking that maybe if I employ a new methodology, use a different process I can streamline the process and well....make it easier to track and control.
And then a thought came to me....what if I use Kanban? Crazy, right? Maybe it would be a perfect fit since in my particular situation I pretty much know what is being implemented, what the end goal is and - well this is not about me or my projects; this is about the key characteristics, "decision makers": Kanban or Scrum? Simplified, in plain English!
Here it is (and you're welcome):
Kanban - think well defined process, like manufacturing, assembly line, in and out.
- You know what your input and output is
- There is a set process that you follow every time - repeat every time
- There is a well defined end result
- If you want to build a cookie cutter software - great! Use Kanban. If you want to develop an innovative cool product that evolves - don't use Kanban
- You can measure your past performance and track it over time
- Think complicated work where you need to define the tasks ahead of time and visually track them
- Think: hey guys, this is the work that needs to be done and here's the timeline!
Scrum - think empirical process, creative, lets evolve and develop as new requirements are uncovered.
- What process? We do something a bit different every time since each product (software/feature) is a new entity
- You adjust constantly, react to changes
- Since each product/project is so different it is hard to establish a solid measurement/baseline
- Think complex work; working in small increments where you continuously reassess whether you should continue with the project or re-plan
- Think: hey guys, they want us to create this, what do you think? Can we do it and if yes, how?
As for me, will I experiment with Kanban? Maybe - yet to be decided.
If you have nothing better to do and want to read more about this topic:
Kanban vs. Scrum
http://scrumcrazy.wordpress.com/2013/02/04/kanban-vs-scrum-kanban-is-not-for-software-development-but-scrum-is/?blogsub=confirming#subscribe-blog
http://www.infoq.com/news/2009/05/kniberg-kanban-v-scrum
http://blogs.versionone.com/agile_management/2012/01/06/1-kanban-vs-scrum-myths-hype/
http://blogs.versionone.com/agile_management/2012/01/06/1-kanban-vs-scrum-myths-hype/