Project Breakdown: How to get the Development Moving again?
An embedded control project did not get off the ground. There was no visible progress and the estimate of the remaining effort until completion remained constant over months. This meant, of course, that the schedule could not be met.
We analyzed the project and found various possibilities for improvement. On the one hand, we analyzed the planning and the organizational processes, on the other hand, we analyzed the technical solutions and development processes.
We provided the deciders with different variants of a possible project flow, from which the development of an MVP (Minimum Viable Product) was chosen, which could satisfy a large part of the end customer's wishes. Although not all lost time could be made up for, we were able to provide products with useful sub-functions for trade fairs and many customers.
From a technical point of view, we have introduced the most clear isolation of the software components, so that developers can work efficiently without too much coordination effort. As development methodology an iterative ("agile") delivery of hardware and especially software was chosen to allow for continuous, efficient integration with the mechanics of the product. The use of tools for version management of all data in software and hardware design has made it clear which components belong and fit together.
Project Scope
Expertise and Technologies
In this project, in addition to our experience in project management and tools for efficient development, it was above all the knowledge of our software architects that led to success.
