Agile maturity assessment and feasibility study of agile product team launch in a large enterprise environment
Agile maturity assessment and feasibility study of agile product team launch in a large enterprise environment
Industry: Energy/Informatics
Objectives, executive summary
Client background and environment
The client is a large Hungarian company with its headquarters in Central Europe, one of the most important energy and industrial players in the region. The company has a presence in ten countries, employs thousands of people and operates across the entire spectrum of the energy supply chain, from exploration and production to processing and end-user services. The in-house IT service provider in Hungary provides IT solutions for the entire Group, from system development and implementation to operations.
In recent years, the company has made a number of acquisitions and opened up new markets, including a significant expansion of its IT portfolio. The organisation is mainly characterised by a traditional project approach, but has also launched isolated experiments in agile themes in some areas. Recognising the potential of agile product teams, management decided to launch a comprehensive survey.
Objectives, tasks
The survey was launched as two separate needs, but due to the interlinkages and potential result linkages, as well as the limited time available, they were implemented in parallel:
- One of the objectives was to assess and analyse the possibilities for setting up and launching agile product teams:
- Analysis of existing IT portfolio with short lead time, mapping of topics relevant for the establishment of a product team
- Conceptualisation for launching and building agile product teams
- To make recommendations to potential agile product teams on the methodologies to be applied
- Definition of roadmaps for the design and development of the identified product teams
- Identifying organisational barriers and necessary changes
- In addition to the domain development roadmaps, to define development roadmaps for the entire global IT area.
- The other objective is to assess the maturity of the agile pilot teams that have been set up in isolation
- Identify teams already working with partially or fully agile approaches or methodologies
- assessing the maturity of the teams selected with the Client
- identification of good practices and areas for improvement
- formulate improvement proposals for existing agile teams
Challenges, difficulties
- Due to the high workload of colleagues on the contracting side, the survey and data collection had to be carried out as efficiently as possible.
- During the survey of existing agile teams, stakeholders asked for support in finding a common understanding of agile concepts and terms.
- The survey revealed that many more teams had started to use agile elements than the organisation had originally thought, so the number of teams included in the analysis had to be filtered due to existing resource constraints.
- A portfolio table containing hundreds of data sets was the basis for assessing the possibilities to build and launch agile product teams, so a special focus had to be put on data cleansing and managing the different types of elements (program, project, small improvements).
- The surveys and analyses had to be carried out with a short lead time of 3 months, which required more flexibility from our team due to the high workload on the client side.
- The organisational stakeholders had very mixed knowledge of agility, so in several places it was necessary to hold mini-experiences (e.g. comparing project and product approaches, or traditional and agile approaches).
- The development tasks were typically carried out by external development teams, which had to be taken into account in the conceptual design.
Implementation of the task
The tasks were carried out in an agile approach, with 2-week iterations and management presentations, given that the content of the final deliverable reports evolved continuously according to the findings of the surveys and analyses.
Exploring the possibilities of creating Agile product teams:
As a first step to assess the possibilities for setting up and launching agile product teams, we held a management meeting to refine the objectives, stakeholders and areas to be explored. Based on this, the organisation exported data tables from its portfolio system, which contained all relevant data on the portfolio elements. In order to be able to interpret the data tables in the right context, interviews were conducted with portfolio managers in each area, which provided input for a first round of filtering and data cleaning and for a proper interpretation of each portfolio element.
Then, in a mixed team building with the designated stakeholders (Product Owner, Project and Portfolio Manager/Scrum Master), a pre-workshop meeting was held for 2-3 hours, where we reviewed the portfolio elements we had already prepared according to the criteria we had provided. This included an analysis of the competences required to deliver the elements, the areas to be covered, the existing team size, the areas of competence required for delivery and the nature of the improvements (e.g. fixed framework, risk level, priorities). The resulting already filtered and prepared portfolio elements were prepared by our team for a workshop.
Following the above exercises, based on the results of the preparation, a more extensive 1-1 day workshop was held, typically with teams of 8-10 people, where each element was covered in detail as follows:
- Capacities and competences needed and available for development
- Team size
- Estimated lead time
- Possible MVPs and their content
- MVP delivery estimated lead time
- Risks
- Opportunities and quick wins
- Support required for the application of the agile approach
The results of the workshop were processed by our team, and in subsequent iterations, the final report was produced, which included the following themes:
- Domain and organisational portfolio map
- agile product team proposals,
- team sizes,
- main objectives, focuses,
- proposed frameworks (simple or scaled agility, Kanban-based solutions),
- proposed team structure,
- MVPs and required competences,
- proposed roles,
- value stream based options,
- the support needed to get started,
- proposed roadmaps for the introduction of,
- organisational barriers and proposals to overcome them with a development backlog and roadmap.
Agile maturity assessment:
We combined the first step of the survey with the portfolio analysis described in the previous section, so that we could list the teams already operating in agile without separate meetings and discussions, and collect information on their development and operation, on the basis of which the managers selected the teams to be included in the survey.
The survey started with an interview, where the assigned project manager or Scrum Master, where the role was already in place, gave information about the team, the framework used and the ceremonies.
After the interview, we scheduled a time with the teams (including developers, business stakeholders, project manager, Scrum Master and Product Owner) for a questionnaire completion of about 2 hours, which was personally supported by our colleagues to ensure the same and correct interpretation of the questions. The questionnaire was a customised version of a questionnaire we had used, which covered the following dimensions:
- Agile approach and principles
- Team dynamics
- Processes
- Organisational dynamics and cooperation
- Product delivery capability
- Business responsiveness
- Organisational adaptability
- Technical excellence and development
After filling in the questionnaire, we observed the ceremonies of the teams, focusing on time frames, objectives, preparation of the ceremonies, content of the ceremonies, the way and level of collaboration, the use of an agile approach and the results of the ceremonies.
The results were then processed and presented in a final report to the teams and the leaders of the organisation.
The report covered areas such as:
- The dimensions examined are team and organisational level values, with a separate analysis of role-specific results.
- Highlighting higher and lower values, complemented by the experience of ceremony observations.
- Methodological suggestions.
- Team development proposals, which were compared with the results of the product team survey.
- Proposed development roadmaps, with a focus on the TOP 3 areas for improvement.
Results
With the completion of these tasks, the organization received a thorough, comprehensive assessment and related action plan, which provided managers with valuable input for organizational strategy planning. Based on the results of the assessment and the proposed roadmaps, the organization embarked on a comprehensive development process, which enabled the conscious and well-prepared launch of additional agile teams within a hybrid portfolio. The developments covered organizational processes, cultural development, employee training and development centers, as well as changes affecting suppliers and IT tools.
