Agile change and transformation
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.
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.
Making decisions in groups like Scrum teams is our daily bread. Together we ponder over the right architecture, we select tools and set rules that we should follow as a software development team. In case of errors we discuss and decide how to get rid of them once and for all. We discuss, exchange point of views, bring arguments… or even yell at each other.
One might wonder why it’s not so easy to adopt agile engineering practices and to achieve technical excellence. When we think of practices, we tend to think of simple things: sticking a shopping list on the fridge with a magnet, having a clear and prioritized list of things to do, and doing them in that order. Why is it then that with Agile practices, things don’t work out quite so well?
The basic rules of Agile project management frameworks like Scrum are deceptively simple. Drawing from his experience as an Agile coach, Jeff Campbell offers in his book “Actionable Agile Tools” some lightweight practices and tools that could help you to implement successfully an Agile approach.
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.
It’s all too common these days to see arguments on Twitter or mailing lists with these rules-bound zealots arguing that ”you’re not agile” because you aren’t following the rules to their satisfaction.
Scrum Expert Copyright © 2009-2025 Martinig & Associates