“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.
If agile started as a software development movement, the customer has been at the center of its values since its initial statement. The usage of agile and lean has now widespread beyond the IT world. In her book “Being Agile in Business”, Belinda Waldock explains the agile and lean approaches from a business perspective.
This presentation shares a set of stories, representing lessons learned from running an agile project in a waterfall-based telecom culture. What was done differently from the enterprise waterfall-based project management standard? What agile principles and specific practices were applied? What were tangible benefits to the business from the situation where one project team became “outlaws” of the corporate culture.
Scrum has long been the most popular of the Agile approaches for software development. But what is Scrum really about? What does a great Scrum team look like? Is Scrum really the flexible, free-spirited collection of ‘frameworks’ that are so often believed to be able to be tailored to suit what works for us? In our attempts to be ‘Agile’, have we forgotten the benefits of structure and discipline? Do we bend Scrum too much to suit us, and what is the impact of this?
What we do in software development is hard. Lots of companies, teams, and people pick up Agile approaches to make it easier, and then realize it’s still really hard. They learn that Agile didn’t fix things. And, then they get to work trying to fix Agile.