Often the processes that deliver both a product and its maintenance, grow to exceed Scrum's capabilities and technique. If you want to keep to the general Scrum workflow, but include service work without causing interruptions, why not try Scrumban: the joining of Scrum and Kanban?
A combination of the two great Lean approaches may lead to an ideal one. Scrumban combines Scrum and Kanban and contains the best rules and practices of both methods. On one hand, it uses the sanctioned nature of Scrum to be Agile, on the other it encourages teams to constantly improve their processes along with Kanban’s aim of continuous improvement (kaizen).
If you’re reasonably well acquainted with Agile methodology, you’ve most likely got a good understanding of Scrum, the project management method associated mostly with software development.
It’s very well established, has its typical roles, artifacts and ceremonies. But there is also Kanban, historically associated with industrial process management, perhaps less known among software developers, but much easier to apply and very useful for work based on operations more than run by projects completion schemes.
But have you thought of the good that may come from joining the two together?
It’s well known, that as far as Kanban audience goes, a lot of it is composed of current Scrum-doers. Therefore it makes great sense to direct the education and information about great Scrum-Kanban hybrids towards them, known as Scrumban. As well as people completely new to Lean in general.
So, whether you’re tired of Scrum or intrigued by Kanban, read about Scrumban to possibly get closer to finding your perfect tool.
Liz’s experience with Agile had started by working with a version of Extreme Programming (XP), very similar to Scrum, just not named as such. She had later familiarized herself with Kanban and grew knowledgable in the Agile approach altogether.
The aim of this article is a practical comparison of Scrum and Kanban, allowing people to get a better understanding of which methodology may suit their process better.
This article had been inspired by the LSSC10 conference, at the beginning if which Michael Sahota, a self claimed Lean/Agile coach, had been receiving mixed messages about Kanban. Some said it’s simply a time for change, hence Kanban, others claimed its more widely applicable than previous methods and therefore needed to be spread. Find out what he learned about Kanban and Scrum and what is his advice for those choosing the methodology right for your team.
Ian has worked as an Agile coach for quite a while and reflects on the fact, that whenever he’s being interviewed for a coaching session, it’s often the manager that he meets – not the team themselves, even though it’s them that he’d be working with. So, he likes to inquire about meeting the team.
Teamwork is often too diverse to be manged using pure Scrum method. The author suggests why a hybrid approach - Scrumban - can work for many a team.
Český
Deutsch
Español
Française
Italiano
Polski
Portuguese
Русский