Three years ago, a presentation of the 2014 PNSQC conference was titled, “How to Fail at Agile Without Really Trying”. It was based on achieving a successful implementation of Agile Scrum by leveraging “lessons learned” from failure. The company in question is now over four years into using the Scrum Methodology.
It is sometime difficult to have an overview of the different principles and practices that are grouped under the Agile banner. In his blog post, Jerome Kehrli has tried the challenging exercise of classifying Agile principles and practices using the periodic table of chemical elements as an inspiration.
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.