Transparency and Project Management

Trust through transparency – the secret of the collaboration between customer and contractor.


Agile methods require a great deal of trust between customer and contractor. This is already apparent in the Agile Manifesto. In order to establish a relationship of trust as quickly as possible, all elements that could hinder an agile project management approach – such as e.g. documentation, contracts and fixed plans – are eliminated or reduced to a minimum.

In this context, the most important measure AOE provides its customers is an unusually high degree of transparency. This transparency includes information regarding the costs, the utilized resources, the tools and processes used, the progress of the project, and much more.

Transparency and project management at AOE at a glance

Budget and Costs

We give our customers the assurance that we will deal responsibly with the promised resources and will use them optimally to successfully implement the product vision. For this, AOE offers clients a detailed insight into the internal processes and, among other things, grants access to the tracking of the development team.

Resources

The compilation of project teams and their use is closely associated with the later success of the project. To ensure an optimal and close collaboration, AOE offers its customers the option to influence the assembly of the team at the beginning of the project. In this way, the client has access to a high-performance team at all times.

Tools and Processes

During the course of project numerous tools are used, that support not only development teams in their work but also product owners and proxy product owners. These tools are sometimes proprietary, but usually Open Source or even tools developed in-house. Our customers have access to all relevant tools during development and thus can always view the current state of development. This ensures a high degree of transparency.

The continued development of processes (in an agile environment one refers to the continuous development Kaizen) takes place with constant customer involvement. In this way, AOE optimizes not only the processes, but also provides training in project management for customers.

Project Progress – Release and Iteration Burn Down

By structuring and dividing software development in different iterations (sprints) with specifically defined requirements, customers constantly receive a current status overview of the solution from AOE. By using sprint- and release burn downs, progress and planned development progress can be observed. In this way, AOE can quickly locate problems such as delays and work on trouble shooting within the framework of sprint reviews and retrospectives.

Example of a Release Burn Down Chart

In the project three releases are planned with a total of 13 iterations of two weeks each. After six iterations, the first release (completion of the platform for content migration) is planned. This release comprises 380 story points. As can be seen, the current iteration Nr. 4 is lagging behind the ideal burn down (green dashed line). However, we can also see that the speed of the team (team velocity) has improved in recent iterations. The release target can thus be adhered to with a high degree of probability.

Do you have further questions about agile methods at AOE? Contact