A great XP2024 conference with agile topics on crisis, AI and all the rest

At the beginning of this month, I had the pleasure of attending once again one of my favorite agile and lean conferences—XP 2024, the 25th International Conference on Agile Software Development in Bolzano, Italy. One thing I appreciate about this conference is the excellent mixture of industry practitioners, university researchers, and a select group of well-known independent agile experts.

Getting to the site from Nuremberg was challenging due to severe flooding in the Munich region, a stark reminder of the climate crisis. Train services were disrupted, forcing me to take a detour through Passau and Linz, with an unexpected overnight stay in Innsbruck due to a missed connection. Consequently, I missed the Wednesday morning keynote by the wonderful Diana Larsen, co-author of the well-known book „Agile Retrospectives,“ recently published in its second, revised edition. Despite this, many great talks were yet to come.

Maarit Laanti delivered two speeches, one based on her extensive experience as an Agile Enterprise Coach and contributor to the SAFe model. In her second talk, „Accelerating the Digital Revolution: Agile Hardware and Sustainability,“ she provided several insightful examples of how companies can benefit from agile methods. She explained how these methods contribute to sustainability goals by enabling development, production, and transportation with less material, less energy, and more cyclic usage of resources.

Semira Allen delved into the heart of Gen Z, convincing us to recognize their potential as torchbearers of agile innovation. While we shared some doubts about how to pave the way for them, she highlighted how crucial it is to harness their potential in our company environments.

Ondrej Dvorak shared his experience of applying Lean Startup methods to a crisis situation, specifically helping people fleeing Ukraine by designing a web portal to connect them with legal support in various countries. His presentation was a valuable reminder of how much can be achieved by a small group of dedicated individuals during a crisis, and how these methods can also be applied to new business ideas in more typical circumstances.

Another fresh voice in agility was Gladys Ng’weno, an Agile Coach from Nairobi, Kenya. She applied her agile coaching skills, honed in her work with software teams, to a cross-functional team in Kenya’s Maasai Mara conservancies. This team, composed of biologists, rangers, and local representatives, aims to balance the needs of wildlife, tourism, and the local population.

Some presentations deserve their own articles:

Yuliia Pieskova, the young CEO and co-founder of AI startup Alpha Affinity, gave an inspiring presentation titled „Agile Coach v.2, Powered by AI.“ We were all excited to apply the strategies and tactics she shared. Additionally, she facilitated a workshop to practice prompts for agile coaches needing technical support. I was impressed by her speaking skills and professionalism.

Hendrik Esser, a well-known expert in agile transformations and scaling at Ericsson, is now the top manager for Ericsson’s Cloud IMS Solution. His new presentation, „Agile and the Management Grind – My Journey to Complexity Leadership,“ emphasized the importance of adapting leadership styles to the complexity of each topic. His lively talk culminated in a table that made the choices easily transparent.

Overall, it was a fantastic experience to be there, reconnecting with great people who have significantly contributed to agility in many companies, including our Datev eG in Germany. Special thanks to Diana Larsen, Maarit Laanti, and Hendrik Esser for their invaluable contributions.

The 25th XP conference was also an opportunity to reflect on past conferences, bringing to my mind especially the teachings of Mary and Tom Poppendieck.

It was wonderful to meet and get to know many new colleagues who are passionate about agile methods and will undoubtedly advance the field even further. Thanks to the organizers and the program team, headed by Xiaofeng Wang—You rocked it!

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