If you have experience in implementing both Agile Scrum and Agile Kanban methods, please tell me their Pros and Cons based on your experience. Thanks in advance. Saving Changes...
Sort By:
Drake SettsuProject Manager / BloggerHi, United States
Before you implement either one you will need to have a seasoned team or a team that will embrace a new method. Weak teams will not benefit from Scrum or Kanaban. I use Kanban to track my goals of the week to make sure I address them. It also helps as things come up during the week to add tasks to your Kanban to keep it on your radar. Kanban is very helpful being a visual tool to see at a glance what you need to do. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Choose based on what is needed to solve the problem or to provide the correct pathway to achieve the goal. The pros and cons will be linked to the specific goals.
Can you provide additional information/background? Current problem, industry, goals, etc. Saving Changes...
Assuming you are not solely referring to the use of Kanban boards during agile delivery, a true adoption of Kanban practices will involve:
* Using different metrics to assess performance. For example, velocity might be replaced by cycle time
* Elimination of sprints and iterations - Kanban would encourage more of a continuous flow of work without artificial time boxes
* Determination and management of limits on how much work can be in a given stage of delivery
* Daily standups might shift from the classic three questions to a focus on impediments
In my experience, many teams start with Scrum but as they mature start to incorporate elements of Kanban into their delivery processes as I do feel it requires a higher level of maturity to successfully adopt Kanban.
It all starts with the mindset. You surely know that a fool with a tool is still a fool. The method won't solve issues tomorrow - it's about humans.
If you have specific points in mind, please share.
Bests
Christina Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I agree with Kiron than Scrum should come before Kanban. Kanban assumes that you are already sufficiently mature to not worry about velocity, deadlines and burn rate. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Beyond great comments from my "discussion-mates" above let me try to add something. Each thing you introduce into your organization will impact your entire organization as a whole. To decide about a method or technique you have to analyze your organizational architecture first and then decide what best fits or the changes you need to make to actual situation. For example, Scrum is a framework not a method then you can fill it with any technique, for example Kanban. That is because some people have invented a new buzzword like Scrumban. Saving Changes...
