Agile India 2014 Conference – large scale distributed agile development

AgileIndia2014_LogoBig
For 10 years, the Agile Software Community of India has been holding this conference now, with ever growing numbers and great names from everywhere. With more than 1200 participants, more than 250 of these from other countries than India, extending from Norway to New Zealand, from Indonesia to Ukraine, and more than 300 women, Agile India 2014 was a huge and really diverse agile conference.
 In the previous years, I had already received positive impressions from the colleagues in Bangalore. This year I had the pleasure of participating for the first time myself, presenting the story of our Distributed Product Owner Team for an Agile Medical Development. The process of selection of topics and feedback was very well prepared and community based. While everybody could see the proposals, ask questions and comment on them, the members of the program committee took care that this would happen consistently, and did a lot of it themselves as well. For the topics selected by them, also an extended paper was necessary with a case study, which also underwent a feedback and approval process, in my case by Ravi Kumar and Pramod Sadalage .
During my presentation

During my presentation

Fortunately, I had work to do in India as well – start up trainings for a few new Scrum teams at our company – so I already had the justification for going. On the other hand, I had enough work to do so that I could not consider going to the other conference days, apart from the one I was speaking at. So I can only talk about the Offshore Distributed Agile track.

Todd Little presenting

Todd Little presenting

I enjoyed Todd Little’s keynote in the morning very much. One of the key messages that resonated most in me was „We need to treat remote teams not as coding monkeys but empowered Ewok.“ I hope as software specialist, you are familiar with the Star Wars universe and do not need to look them up in Jedipedia.Todd said exactly what we are trying to do in our big, distributed product development, and my mission to Bangalore was part of it: make the remote teams self-organizing, trusted members of our diverse product development universe. Only that in Todd’s presentation, it turned out that he only needed to add a few software developers with a domain specialist in Romania and a small test automation specialists’ team in Vietnam to his original group in the US – and they were already very successful. So: adding the right people for a good reason, valuing the individuals over corporate strategic outsourcing strategies.

The other talk I remember well was from Rajkumar Anantharaman from Intel, who stated „If you want to go lean and agile, first you need to get rid of Excel and PowerPoint“. This was of course not aimed at a nice PowerPoint by the Product Owner showing some functionality the users ask for, but at getting rid of the additional reporting needs that keep teams busy with overhead.
The venue was a bit resisting the actual number of people participating, it is certainly difficult to predict, but maybe another year they will be better off in a congress center. A difference with the European agile conferences I have been attending like ALE or XP was certainly that there were much more business-people than agile coaches hugging each others. Maybe even most agile coaches look like business people in Asia. In all cases it is very important going to India and seeing what is going on there, noticing how people discuss, what they hold as granted in agile, and what they have still doubts about.
At the panel discussion with Doc Norton (groupon) and Chad Wathington, ThoughtWorks Studios

Participation in the panel discussion with Doc Norton (groupon) and Chad Wathington, ThoughtWorks Studios

More or less, the other speakers confirmed what I have learned from our own experience: there is not the question whether or not agile is going to work with distributed organizations and teams in India, but how to make it work. You can do a pretty lot of things right or wrong, and even terribly wrong, but you can just as well be successful if you are doing many things right.  At the end of the track, there was a quite interesting panel discussion facilitated by Naresh Jain: Offshore Agile…An Oxymoron? There were a lot of interesting topics discussed. Where I could definitely contribute was when someone asked the panel whether they could just take a framework like SAFE and apply it to a big distributed product development organization to make it agile. According to my experience, though such frameworks can help, every organization has their own challenges, their constraints, and their organizational culture. Whatever lean-agile framework they will build, they need to build it on their own – but of course, taking as input the experiences of others, and agile frameworks as well as wonderful books like Bas Vodde’s and Craig Larman’s „Scaling lean and agile development“.
Photos used by courtesy of  Agile India (c)

Large Scale Agile at XP2013 Vienna – exchanging knowledge at a great conference!

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.

image

(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
· Culture
· Practices and process
· Structure

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.

image

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!

Best Regards
Andrea

Slides for ScanDev 2013 DONE: distributed product owner team – strategies

One week to go for this year’s ScanDev conference in Gothenburg, and slides are done.

image

Topics covered are mainly:
Strategies for growing a distributed product owner team, when the problem space is very different from the normal experience world of a software developer. Strategies for communication and customer collaboration in the distributed setup.

For preparation, I made a lot of personal interviews with product owners on different hierarchy levels and multiple sites. I learned a lot about the reality behind our official agile framework, and how much the real success depends on people and their skills and goals.

To convert my knowledge into an interesting presentation I used a marvellous book, a classic: Presenting to Win: The Art of Telling Your Story by Jerry Weissman. What is very helpful in this book is that he tells you a lot of stories to make sure you know what you want to tell, to whom, and how you will bring this across to your audience. So I started to create my presentation on a lonely day at home, using hundreds of sticky notes on my personal whiteboard, instead of bothering with Outlook templates or -beware!- assistants. Then I selected a structure for the slides that would allow me to tell my story, and then I created each single slide on a sheet of paper, put them into the structure, re-ordered and finally bright them to the office.

image

There, of course, I had to take a corporate template, and also picked a lot of photos, that would this time nicely fit with the topic. As structure I had selected a pyramid. I created it with corporate colors, and let it build up throughout the slides.

At the beginning of this week, it was finished, and I submitted it for review and release. And -wow! -I got it released after considering a few remarks, in less than two days. I can say, the release process got much more agile since I first used it for an external presentation four years ago, when it still took me four weeks, but obviously as well my own professionalism in creating publications has increased a lot since then.

Speaking at ScanDev 2013 about our Distributed Product Owner Team @ Syngo.via

I am speaking at SCANDEV 2013

This week I received the news that my new talk has been accepted for SCANDEV 2013 on March 4th to 5th in Göteborg, Sweden. The title is „Distributed Product Owner Team @ Syngo.via“

What is it all about?

We are developing medical imaging and workflow software in an agile way with development teams distributed to several countries. One of the major challenges is how to set up and communicate within the Product Owner team.

  • There we have to deal with the distribution, e.g., have the Product Owner either onsite with her peers or with her Scrum team, travelling, or with proxy.
  • We need people who are good in two different fields of knowledge: medical and software development.
  • As a third issues, the environment of the customers may be different in different countries.
We have ramped up local Product Owners in different countries, have found local collaboration customers, and have developed  a set of communication channels and workshops how to synchronize Product Owners in the team, share a common vision and backlog with their Scrum teams, and collaborate with customers locally and globally.
While I am putting my presentation together, I would be interested very much in what my customers want to know about. You can ask me questions, and whatever is feasible I will include into my talk. So Product Ownership is being directly applied.

An incredibly intensive 1st ALE2011 Unconference – Agile and Lean Europe in Berlin

 (Olaf Lewitz, one of the central organizers, on a photo by Marcin Floryan)
In February, 2011, the Agile and Lean Europe network was founded in LinkedIn by Jurgen Appelo, Author of Management 3.0. He asked the European lean and agile practitioners and communicators to join. We were about 1000 members within a month, and there were lots of active interesting discussions, “bathtub conferences” and many ideas how to collaborate more closely. The first real-life meeting happened at XP2011 in May in Madrid. Since then, 47 people with a vision created the best and most intense (un)conference I have ever attended. My own role was to be part of the “industry sofa” – we had “sofas” instead of “chairs.” I spent some of my free time reviewing abstracts and finding out whether these people were good speakers, if I had not heard them speak before. The final result we composed is amazing – http://ale2011.eu/speakers/ .
audience!

    The audience was amazing

All further work was organized via real-time collaboration tools: Skype, Basecamp, GoogleDocs, Mindmeister, Twitter, and Conftool. Real-time mostly meant evenings, sometimes even weekends. The final event structure included one keynote every day – with Rachel Davies, Bjarte Bogsnes and David Snowden, we had three highly interesting speakers, two of which are not from the software world, but are teachers of lean concepts for management.  Each day started with a funny coding dojo warm up, followed by 30-minute talks in the morning, lightning talks after lunch, and Open Space all afternoon. Virtually everybody participated actively in something: more than 220 people from at least 27 European countries. Talk topics ranged from “Software Craftmanship” and “Metrics in a complex world” to “How to change the world.”

Bjarte Bogsnes from Statoil, Norway
For me, Bjarte Bogsnes with his “Beyond Budgeting” talk was most inspiring (http://ale2011.eu/2011/09/17/ale2011-keynote-bjarte-bogsnes-on-beyond-budgeting/ ), but… yes, but… the 7 levels of hierarchy between me and the CEO of our company make me think that this is not the easiest thing to put into practice by myself. Fortunately, many other talks also had inspiring contents!
From Henri Kivioja from Ericsson, Finland, I learned how we can guide managers to practice go and see with the Scrum teams: they just got rid of all kind of upward reporting from project to line managers. They also reduced their full test cycle dramatically, from about 1 year for the whole system (100%) to about 1 week for 90%.
dojo2Eva Kisonova and Sabine Canditt presented a funny game of cultural differences they have practiced with our Scrum teams in Slovakia. It showed the stereotypes that may exist on both sides, which can make collaboration difficult if the teams have not reflected on them. Putting it into practice in a small example among the participants was really fun.
Rob van Lanen explained why and how they had realized FedExDays with his company’s developers in the Netherlands. This is a 24-hour slot, in which the developers can develop whatever they want – the only condition is that they must present it after that time. The department provides food and drinks, and the CEO is present at the demo at the end. The participants created 4 products, a traffic light tool for the software build, and a gaming application. They self-organized to do Scrum in one-hour slots and even pair programming. It was a great motivational boost for the teams.
Claudio Perrone gave an excellent introduction to A3 and Kaizen, which can actually be understood when you look at this outstanding presentation: http://www.slideshare.net/cperrone/a3-kaizen-heres-how. In this way, continuous improvement can be introduced on all levels: in the project team and on organizational level with the managers. This is something we should put more emphasis on soon.
Torsten Kalnin explained how the Wikispeed team builds modular speed cars using very little fuel with lean and agile virtual collaboration of volunteers around the world – an amazing example for agile hardware development – see also at http://www.techflash.com/seattle/2011/02/the-future-of-cars-and-everything.html.
I visited a few more talks related to big agile transitions, offshore and distributed experiences, which we later followed up with discussions in the Open Space.
Open Space facilitated by Mike Sutton
The most intense part of the unconference was surely the Open Space sessions: everybody posted his/her topics at a common marketplace, and there were a lot of different spaces in the venue where we could start discussing around a flipchart. On the first day, I proposed a talk about organizational impediments, to get stories of what happened and how people actually resolved them.  Later, I was in another big agile transition discussion, and there I met a couple of people who also used communities of practice in their companies. So I had my topic for the next day: how to get CoPs going, and how to keep them alive in their original sense, as a means for knowledge acquisition, best practice exchange, and as a catalyst for improvements.
You can find almost all references from the conference in two places: http://ale2011.eu/resources/ and with #ALE2011 on Twitter. A lot of lean and agile conferences in the next future will be powered by the spirit of the ALE-Network, I am sure! 
DSC_6380 ivanKostial JurgenAppelo respect4people
Andrea Heck

XP 2011 Open Space session: Teaching TDD to a Team so that it sticks

On XP 2011 conference in Madrid, I invited to an Open Space session named „Teaching TDD to a Team so that it sticks“. I stated the problem below, and a couple of interesting people showed up and gave very helpful hints, among them Charlie Poole, the inventor of NUnit, as well as Patrick Kua and Alexandru Bolboaca. I have integrated some hints from an earlier discussion of the topic with Emily Bache and Johannes Brodwall at the ACCN in Oslo.
The problem description:
Let’s take a couple of Scrum teams who have already been doing Scrum for a while, but are still lacking some technical practices. Agile coaches are convinced that Test Driven development (TDD) would help them create better and more solid code.
Some have had the opportunity to attend a TDD or XP in general training session, but only very few have taken back something to their work.
What could be the reasons for that?
·         TDD is not intuitive, but you have to practice a time to overcome the first problems
·         If they are the only ones in their teams, it is difficult to stick to it, not having whom to ask
·         There is also pressure to take on constantly work from the product backlog, and work will be first slower than without TDD – they need the consent of their Product Owner
·         Maybe it has not been communicated enough that management and Product Owners would tolerate some initial productivity loss, and at which time
·         The examples from training were easy, but the own project is really hardcore programming J
·         In some project setups, it may not be the same developers who profit from good code, as bugs are corrected by someone else => no closed feedback loop

How can we now bring a good training/coaching solution in?

·         All participants should be voluntarily doing the training
·         The training should be done focusing on one team at a time
·         The training can be 2 or 3 days off site – not in the normal work environment
·         To explain TDD well, code examples that are not from the own project are used at least the first 2 days
·         it is helpful if code examples are from the main programming language that the participants are using
·         The proper UT frameworks need to be installed on the developers‘ machines when they are starting
·         A code retreat could be used for the first phase – this is a couple of developers sitting together and working on the same problems several times, deleting the code in between – outcome is that it is reasonable to create good maintainable code
·         A coding dojo is also a good technique – a group of developers solving a problem, doing TDD, but only one pair at a time will actually work on the code, while the others can look on the projector, and one dojo participant will change from time to time
·         After the participants have some good idea about TDD and first practice, it will be good for credibility and transfer to their own work to look at some own code examples from the team’s real life project
·         The trainer needs to prepare for that, so he/she can work with that code
·         The workshop needs to bring the mindset change to “it is fun working with TDD”
·         After the initial training,  there must be an agreement with the Product Owners how much time can teams spend per week/per iteration on practicing TDD
·         Follow-ups take place in the normal work environment: coach pairs with people in a team on real programming problems
·         From time to time a code retreat or coding dojo to learn more interesting things (refactoring, cleaner code) and practice TDD in volunteer group will lead to strengthen the practice and amplify the learning

XP 2011 conference in Madrid: report of a newbie

Well, I have to admit that while I have been attending and even presenting on a couple of software conferences in the last few years, it was the first time I visited an XP conference. It was kind of that the idea struck me early in April 2011: there is an XP 2011 conference going on inMadrid, soon, they will talk about globalizing agile – this is just what I am doing in my daily work and what I am interested in, and on the other hand, XP means technical agile practices, and this is what our teams still need to develop more.

The intutive decision turned out to be quite good. I met many interesting people – some of the already known from ocasions like the AgileEastern Europe conference in Kiev, the Scrum Gatherings in Stockholm or Munich, or small events like the Agile Coach Camp Norway, or even from Siemens-internal agile conferences some years ago. And I met quite new persons, at least for me, who enriched my view of the agile world.

 

The XP conference seems to build a unique link between industry practicioners and university investigators. It is great to see how the Master or PhD students profit from the direct discussions with people who have global agile experience in the industry. On the other hand, it gives the industry people quick access to new research results.


There are several topics where I found particularly interesting information:
  • Agile and Leadership – here to mention the keynote from Esther Derby and the presentation from Jurgen Appelo
  • Industry reports – Even the ESA converted from waterfall to agile, as reported by Rui Santos and Marc-Elian Begin. In companies, I have now seen several times seen the agile release train by Dean Leffingwell applied – also in the report by Gabor Gunyho from F-Secure.
  • Agile coaching – a very practical workshop with Patrick Kua I had the pleasure to particpate in.
  • The initiative for creating a vision and rules for the recently born Agile and Lean Europe network (ALE) – and a lot of activites following up, including a new conference rotating through European countries, starting September 7.-9., 2011 in Berlin.
  • And last not least the results of my open space inquiry about Teaching TDD to a Team so that it sticks.

I will follow up to these topics with separate blog entries in the next couple of days, starting with the TDD open space.

(photos by Hubert Baumeister)