From my perspective, the 14th International Conference on Agile Software Development XP2013 in Vienna was a great success. It took me to another level of confidence about what is needed to create and sustain a large scale agile organization.
The XP conferences are traditionally about programming and testing in an agile – XP – way, and organizing the team so that it supports XP practices. But they have grown into a conference that also covers product ownership and design, leading agile teams and organizations, and even extending agile to the rest of the organization – this is agile real life in the industry. What I like very much at XP conferences in general is the good mixture of experienced agile people from industry, some very well known consultants, and a lot of academic researchers who also are working close to industry about agile topics.
(Photo: Hubert Baumeister)
On the first day I got absorbed by the Executives & Managers Track with firsthand experience from four different companies: ABB, Ericsson, Johnson Controls and Nokia. Most valuable! The managers were speaking openly about what it takes to get agile, how their company transformation programs took one step after the other to establish agile on all levels. And this is still an unfinished journey, but it has a clear north. An important point from the talk of Hendrik Esser, who is Head of Portfolio and Technology Management at Ericsson, is
To embrace change, you have to change 3 things together
· Practices and process
You should never see agile as a process only, this will inevitably lead to failure. The most important cultural foundation for the agile transformation is building trust, and on top of the trust you can build transparency.
These three important transformations were mentioned by Per Branger from ABB in Sweden, but are basically identical to what Ericsson is doing:
· Continuous Portfolio Management
· Continuous Release Management
· Continuous Development
When they noticed at ABB that they are really a big software developing company, coming from a background of electrical engineering, they launched a massive knowledge and skills improvement program. The remarkable thing is that they measure progress by self-assessment of every developer against description of expected skills, and that the training comes in small portions and by self-assignment as well. Wiki based knowledge bases and Q&A tools that remind a bit of the famous stackoverflow website support the learning as well. “Carrots, no sticks” opens also the path to using common tools.
Gregory Yon is Agile Coach at Johnson Controls and talked about how he is extending agile into the rest of the organization, to the non-development teams as well as convincing different levels of management from the agile values and needs. From him as well as from the other managers I learned that we can never communicate too much to higher management about the advantages of agile, and that we need to measure things and compare with previous projects to show how we have advanced since the old times of waterfall.
Jorgen Hesselberg, Senior Manager, Enterprise Agile Transformation, Nokia (Chicago US) explained how they are using on all levels Agile Working Groups, mixed from management and project roles, to start and sustain agile transitions at each Business Unit, and keep them up and to extend agile to the whole company. The positive results of agile on the results as well as on the employee motivation are impressive.
My own presentation on our Distributed Product Owner Team for an Agile Medical Development was on the second day, and I loved the discussion with a couple of other speakers and participants about the needed knowledge and skills for this role, and the needs for communication in the PO team and with teams and customers. I have also learned that there is actually an open group of experts from industry and research with the goal to foster software product management excellence across industries, the International Software Product Management Association (ISPMA) , who are interested in collecting such practical experience, and are creating resources for professional software product management training.
At the academic track, I found a couple of presentations on the last day very interesting: A research paper by Jeanette Heidenberg, Max Weijola, Kirsi Mikkonen, and Ivan Porres – A Metrics Model to Measure the Impact of an Agile Transformation in Large Software Development Organizations asks whether an agile transformation was worth the effort. For this, they were looking for metrics that support agile values, focus on the whole organization, not individual or teams, and are applicable to both waterfall and agile projects. Also they should be feasible to collect for past and ongoing projects, in any size of project, and be objective and clear. They did an iterative approach with first formulating the goal, then ask practitioners for metrics used, compare them against their values and goals, and finally select a collection of metrics. They have some really helpful metrics that we can apply to learn how much we have already improved through agile, at least in some aspects.
The paper Continuous Release Planning in a Large-Scale Scrum Development Organization at Ericsson by Ville Heikkilä, Maria Paasivaara, Casper Lassenius, and Christian Engblom was complementing very well with the talk of Hendrik Esser, as they are exactly describing how the release planning for individual features works, and which experiences people at Ericsson had with this method.
Of course there were also great keynote speakers at XP2013 in Vienna, a helpful Open Space, a wonderful conference reception, and great conversations in the breaks.
As always, thank you very much for the photos, Hubert Baumeister.
The next XP conference will take place in May 2014 in Rome, which is also a nice place to go to. I will convince some of our colleagues and managers of submitting a talk and participating – we have a lot of experience we can share!