In my team I want to move from Scrum to Kanban. I’ve found that Scrum was not working for us due to the following reasons: – estimations meetings were taking long time, and were very inconsistent (e.g. 3 days of work of development were estimated 3 points, while 4 hours of testing were estimated 2 points) – refinements tooks us 2hrs to estimate 2 tasks – retros were often a never-ending discussions what was wrong – etc.
… anyway, long story short, I suggested my team to go with Kanban, but few guys were against, with following comments:
“we need sprint goal to be set, otherwise we won’t know what should we do?” (I explained that items in backlog will have a description what should be done, and on top of it, I expect some common sense from team members to know what to do [they are senior level])
“in Kanban we need to have everything or majority defined up front and it is good for waterfall projects” (wtf? I explained that I disagree completely)
“there is no thing like ‘common sense’ in software development, because everyone have different priorities” (I explained that order of backlog defines the priority, and if doubts, just talk and ask)
“we still need to have meetings” (I explained that in Kanban we will have meetings, just less formalized than in Scrum)
“we need to be recognised” (I explained that we will do demos/reviews whenever part of application is able to be shown)
So… What do you think about Kanban vs Scrum? Is Kanban really (as I think) easier than Scrum? How do you see comments of my team members – do they makes sense or are ridiculous?
submitted by /u/bzq84
[link] [comments]