Scrum or Kanban?

Nima has years of experience in coaching teams and championing continuous improvement. He applies double-loop agile to coach teams and help them build up flexible cultures. Nima has worked with a wide range of clients from small start-ups to big corporations. Previously, Nima worked as a Scrum Master and as a Product Owner, and successfully launched a vast array of products from light iPad apps to giant enterprise solutions.

You apply agile to software development project management because you and your team believe it fits today’s business needs better than how other framework. But you are not sure what methodology is the best for your project. Should you always use Scrum in some way? Is it versatile enough to adapt to any situation? Or are there other agile methodologies that work more efficiently under some conditions?

Many organizations always stick to one agile methodology, mostly Scrum (after all, it is more convenient to train and manage one methodology). This approach reduces complexity and makes management easier. Great idea, right? Wrong.

Like many other things in life, the easiest solution is not always the best. It is more effective if you choose the best methodology for each single project based on its nature. Scrum doesn’t fit all projects’ needs. Kanban is another agile methodology that, believe it or not, works more smoothly for at least one type of project. But what type? 

Kanban, Continuous Work
In contrast to Scrum, which is time-boxed, Kanban advocates continuous work on tasks. When new tasks come up, the team evaluates the scope and creates acceptance criteria. Then each task goes to a queue (called “not started yet” or “to do”), waiting to be grabbed by a team member.

Once a developer takes that task, it will move to …

Please log in or sign up below to read the rest of the article.


Continue reading...

Log In
Sign Up

"I may not agree with what you say, but I will defend to the death your right to say it."

- Voltaire