Organizations often start with Scrum after having heard about it, read about it, or after having read the Scrum Guides. While that is great, there are several unforeseen challenges they often face that prevent them from really benefiting from the advantages of Scrum. This presentation discusses seven unmentioned challenges of Scrum and uncovers possible solutions.
Agile change and transformation
Shoddy software quality, disgruntled customers, missed deadlines… Such is daily life in many software companies. But there exists a better way. This presentation tells a story of turning around a demoralized and disengaged group of developers into a high performing team, while improving software quality, customer satisfaction and reducing technical debt.
The Agnostic Agile Oath is a movement that aims at recognizing the importance of being agnostic with agility at any level. As it is stated on the web site: “one size does not fit all, one framework is not the answer, and the what’s and the how’s of what needs to be done, should be suited to customer context and to a wider strategic vision.”
If one of the first aim of Scrum was to break the silos between business analysis, development and testing, you can consider that improving the cooperation with the operation side of IT as the next frontier in this journey. What is the point to produce potentially shippable software increment in two weeks if your database administrator doesn’t want more than three new releases windows for the production database?
“Agile has become overly decorated. Let’s scrape away those decorations for a minute, and get back to the center of Agile.” The Heart of Agile is a fresh look at Agile that strips away a lot of the cruft that has built up over recent years. Collaborate, Deliver, Reflect, Improve. Alistair Cockburn goes over the addition of kokoro onto the shu-ha-ri sequence, and its implications for agile.
Resistance to change is part of the human condition and overcoming this resistance is part of adopting Agile & Scrum and changing the way delivery teams work together. A large part of the prevailing certified methods are about tackling this problem in a variety of ways. How successful these methods are depends on many things and not least the starting conditions and senior leadership support. Without this kind of safety net creativity is called for and Tony Heap talks here about his experiences with a less head on approach to influencing things.
Agile versus Waterfall is often presented as a difference in development methodology, but it is much more a clash of cultures. Large bureaucracies, government regulation and many other factors can create an environment that is hostile to many forms of innovation and in which Waterfall is actually the most cost-effective approach.