If the title of this book is a clear reference to the current trendy approach in software development, readers should be aware the that most important part is maybe in the subtitle “Systems Thinking and Organizational Legacy”. Not that Agile minds will be disappointed by reading it, but this book discusses the more important fact that from time to time software developers tries to adopt a new set of best practices and most of the time they fail.
One of the key benefit for organizations that adopt an Agile project management framework like Scrum should be the shortened value delivery cycle. Providing a quicker feedback, this should lead to continuous improvement the development process. This is however not always the case. In this article, Ronit Eliav discusses six issues that can cause static Agile.
Individuals and interactions over processes and tools” how often have you heard this phrase from the Agile Manifesto? I strongly believe in it however we see that a good balance between the two parts is the key to succeed. As the Agile Manifesto says “That is, while there is value in the items on the right, we value the items on the left more”.
Some software development teams try to adopt Scrum, but they don’t achieve the full benefits of this approach. This might be due to the fact that the teams customize Scrum in a way that is inappropriate. In this article, Pablo Pecora suggests five aspects of Scrum, like the planning poker, that you cannot skip if you want to get the benefits of Agile.
This talk explains the need for continuous improvement when adopting agile ways of working. It explores how continuous improvement is fundamental in agile, and what you can do to increase the agility of your teams and the organization as a whole.
Should agile practitioners avoid large corporate clients? Are they just too hard to take on a progressive agile journey? Helping companies that think they are already agile to actually adopt agile is an interesting challenge, for a start, nobody likes to be told that they are doing it wrong. In this video, David Espley shares his experience of helping larger corporate clients to act more like Lean startups, discusses how you wean people off their agile washed legacy processes and let go of some of the big company baggage.
Agile is about giving responsibility to the people, and self-organization is one of the way this is achieved. Agile is also about continuous improvement and adaptation. To follow this journey, the Scrum teams need to assess how they are doing and where they should improve. In this article, Ben Linders discusses Agile self-assessments and how they can support the continuous improvement process to an Agile mindset.