The agile transition of DATEV‘s product development organization has started.
DATEV was founded in 1966 by a visionary tax consultant as a common IT backbone for himself and his colleagues. The then recently emerged mainframe computers promised to solve their common need for correct calculation in a world of increasingly complicated and ever-growing legislation. – This bold idea transformed the initial startup into a constantly growing company in form of a cooperative – the main customers are also the owners of DATEV, therefore it is called “DATEV eG” in German. Today, 40 000 tax consultants in Germany are DATEV members. 12 million employees get their monthly pay slip via DATEV software. The members use DATEV’s financial accounting software on behalf of 2.5 million small and medium sized companies. DATEV’s own financial numbers have been in the black every single year since its foundation.
The customer feedback has been positive over many years, with software solutions which are not always easy to use but contain the correct implementation of complex legislation. Now we need to evolve towards new web based products which will support the digitalization and automation of the members’ daily workflows, as well as providing faster customer and market feedback cycles. So the purpose of the agile transition should be clear, yet it is not at all easy to create a sense of urgency among the middle management considering the success story that is still true today.
In 2016, we created a learning event for the approximately 200 middle managers. We designed a two day event with two main goals:
- The managers should understand the challenge of DATEV’s digitalization strategy
- They should learn that an agile transformation is needed in order to support this strategy and that they would play an active role in it
The methods we used for this event were a combination of:
- Very short speeches by the top management supporting these goals
- An information market where the first projects in which prototypes of new digital products had been created were presented in a self-organized way by team members of these projects
- The managers selected the most important obstacles these projects were facing, to be solved by themselves, and started working
- A retrospective-like setting in which the managers analyzed and started to develop solutions to these problems
- The whole event was facilitated by team members who were recruited from the company’s in-house agile community
The outcomes of this first event were three working groups working on the most important obstacles according to the voting of the managers, and a quite positive feedback.
The overall concept of the two-day event was rated between very helpful and not helpful at all – in 6 steps. More than 80% of the participants chose the two best ratings. They were especially pleased with how well the event was facilitated by the team members.
One feedback given during the event to the top management was that direct communication with the team members must take place more rapidly. The top management promptly put this into practice on the second day of the event by finding and announcing a date for an information event for all 1800 team members.
All three work groups working on the top three problems developed results in the following weeks, which were presented and discussed in a second event. The third group working on “goals, metrics and a master plan for a complete agile transition” initiated a thorough analysis of the situation, resulted in the top management forming an agile transition team and calling everybody to action during the second event. There all sub-organizations started their own agile transition teams and plans.
Still the development organization as a whole is overburdened with work due to a big upfront planning process in which all of the work for one calendar year has been defined and estimated and committed by the management until July of the previous year. This was the fourth problem addressed by top management itself. A team worked on this process during the next couple of months, with the goal to rely on rough roadmaps instead and to introduce three-monthly portfolio planning cycles. Now in a third event end of April 2017, we have worked with the managers on this topic in order to get everybody into re-defining their current product development goals so that they can be measured and sliced down into smaller sub-goals which result in deliverable slices of products.
Interested? You can here more about it on Thursday May 25th in my „Creating an agile learning experience for 200 managers“ presentation and workshop with Christina Busch at XP2017 conference in Cologne.
Andrea's Agile Reflections 