If Scrum isn’t going that well, and you’re hitting problems and challenges in your organizational environment, the good news is you’re normal. It’s very common for teams to have significant challenges getting started with Scrum and other frameworks, because it involves a shift in mindset.Read More
The Agile work environment is an environment that supports Agile ways of working and Agile ways of being. Naturally, the next question is, “Well, what does that mean? What kind of characteristics make an Agile work environment?”Read More
If Agile is like dessert, Scrum is like ice cream. The phrase “Agile vs Scrum,” is a bit of a false dichotomy. Scrum is a subset of Agile, just as ice cream is a type of dessert. And Scrum is a very specific kind of dessert – say, vanilla ice cream. It’s this really popular way of doing dessert – or in this case, doing Agile. And that’s where people can get confused.Read More
If you are having culture challenges with your organization, you are not alone.
80% of participants at a recent conference (Scrum Gathering in Orlando) reported that the dominant culture in their organization is not supportive of progressive working environment such as Agile.
One of my clients was struggling with Kanban vs. Scrum as a starting place. They really like the energy of Scrum: teams, collaboration, learning but from a workflow perspective needed the adaptability of Kanban: urgent requests, different ticket types, able to change direction quickly. This happens when the management and culture is there but there are too many short-term needs and/or external dependencies.
Four years ago, I argued that Agile is a Culture System focussed on Collaboration and Cultivation. We may build on and refine this understand to see that Agile points towards a higher level of organizational consciousness and the benefits that come with it. In particular, Agile is about valuing people and setting them free to deliver.
Scrum is the most popular Agile methodology with Kanban a growing second choice. Learn about the core parts of each one as well as how they differ so that you can find the best fit for your team or organizational context. For example, Scrum is great when you want to shake up the status quo and transform the way you work. Kanban is great when small changes are a better fit for the environment. Learn how they work and how you can use them in your environment.
I was at a client recently and one VP was convinced that Agile was “untrue” and there was no way it could possibly work. The problem was that he had never heard of backlog grooming or getting stories ready. Once he saw the infographic below, the penny finally dropped and he understood how this crazy thing called Scrum can possibly work with user stories.
Guest post by Michael DePaoli
If your development team or manufacturing team is considering moving to using Kanban vs. Agile Scrum, one of the biggest decisions is choosing the right agile development methods for the job. Let’s discuss the realities of implementing Kanban and some of the fundamentals that hold back both Kanban and Scrum implementations.
Process: Everyone built a model for an acceptance test and each group voted to select the two most valuable acceptance tests. So there are four acceptance tests in total.Read More