Lessons learned in Agile

It´s now more then one year already that I´m working for Agile Partner. Here are my personal insights that I gathered during that time. Not that much revolutinary, or even new stuff, but I experienced that it is a completely different thing to read or hear about these things, or to discover and learn it for yourself:

  • Retrospectives are essential. Give the team room and time to lean back, inspect & discuss. The outcome (= improvements) will be worth the investment of time.
  • Change in small steps. Don´t try to achieve everything at once. It´s easier for people to adapt a small change at one point in time, then to try introduce huge changes to the workflow people are used to. Instead change small, and change often, if you feel there´s still room for improvements.
  • Don´t argue about the people in your team. They´re the best you have, and the they´re all you need. “Whoever comes is the right people”. They will do what ever is needed to get the job done, and they will get the job done well.
  • You can´t force a self-organizing team to do anything. Even if you know that your proposal/ idea would improve things. If the team´s not ready yet, it is not ready. If the team feels it´s necessary, it will introduce the change sooner or later via the retrospective.
  • Don´t insist on your ideas/ proposals/ way of working. It´s more important to find a consense everybody can work with then that you´ve been the winner of a discussion. And it will be even more succesful on the long term to go the way that has been decided on by the whole team.
  • Your scrum/ agile implementation will change over time, as your team learns and as it is getting more and more mature. There´s nothing bad about it. Why do “scrum by the book” (by the way which book in particular?), if there´s no other reason then “the book”. As long as you´re still respecting the agile manifesto, everything will be fine.

What are your Aha-moments from working within agile teams? Please share them in the comments, we´re most happy to discuss!

2012: Agility should win by a utilization rate of 80%!

As we enter 2012, it seems appropriate to revisit a Strategic Planning Assumption made by Gartner in 2010.

By 2012, agile development methods will be utilized in
80% of all software development projects

Drafted by Gartner when entering 2010, this document gives arguments like:
Existing groundwork
The tools needed to support an agile transition become and will become more and more mature while the development teams will desire to come out from heavy development process.
Visible benefits
Organizations that have made ​​the shift recognize that the main visible benefits are the improvement of the productivity and flexibility of the teams but also the reduction of the costs of development and maintenance cumulated.

Necessary warnings related to challenges that organizations will have to face are mentioned like:
Cultural changes
The companies will have to take into account some key cultural elements like among others the team-focused and collaboration cultures, the needed of dedicated resources, the speedup of defects detection…
Achievement price
The price to continue benefit from agility will be concentrated in the necessary investment in training and coaching of teams together with the acquisition of tools enabling the transition.

Finally the utilization of agile development methods seems to be considered as a key driver to avoid in long-term the declining of product quality and to allow a better understanding of the project by the business.

To read further get here the document