In a recent, well written but smallish study, a team of researchers from Finland have tried to find where KanBan has benefits. In their setup, teams of master students were instructed to use KanBan in their software development projects and then interviewed about their subjective perception of the benefits of KanBan. For a full description of their research methods, please read the original article.
What the researchers did find was at least some support for the following effects of KanBan: Continue reading →
I agree with most of what is said in the podcast, especially that there is no “one size fits all solution“. Different teams have different needs. Some people need Scrum, other Kan Ban and yet others just a general idea of how to do Lean.
Requirements are highly controversial in software development. There is always too much and too little requirements. They are often blamed for project failure or seen as required for project success. I have seen cases where there were too detailed and complex requirements. The result was that everyone worked around the official requirements and used other more informal requirements. I have also seen cases where the requirements were way to unclear. It became impossible to know for certain what they meant or when they had been met.