What can a product owner do?
A new role in the AGILE methodology is the so-called product owner. He is responsible for the market requirements (market), the product architecture (technology) and for project management (project). In most companies, the market requirements are defined by a product manager. For the technology, i.e. for the product / system architecture, many companies have created the role of the so-called system engineer. The project manager is responsible for Q, K, T (quality, costs and deadlines).
Thus, all essential dimensions for successful project management are mapped.
Why 3 rolls?
People who fulfil this broad and deep profile of requirements are rarely found in one person in industrial practice. For this reason, we have developed the Product Owner Team (POT) from the individual Product Owner. The POT consists of: Product Manager (Market), System Engineer (Technology) and Project Manager (Project).
The idea of the product-owner team has enabled us to achieve a significant relaxation in the companies: None of the three roles has to fear under- or over-employment, the search for the one “extreme qualification” is eliminated. Moreover, no new function needs to be created.
3 essential advantages.
1. the project manager is not alone, project management takes place in a team. The three relevant lines of vision – market, technology and time/cost – are staffed by professionals from each field. No one sets the goal unilaterally or independently of the others. Three sparring partners work together every fortnight on the best sprint goal for a team. The quality of the target definition increases.
2. the market is integrated. In most companies, the active role of the market, i.e. product management, is essentially reduced to the creation of specifications and the market launch. At AGILE, the market is confronted with the capacitive possibilities of the technology every fortnight. This puts an end to the long list of wishes without a regulator. Strategy is the art of doing without, and this becomes very concrete at AGILE: product management is involved when priorities are set in the backlog before each sprint.
3. In many companies, the system engineer is a key figure who combines interdisciplinary knowledge (e.g. hardware, software, mechanics). Often there is no career path for this. Experts are promoted to group leader, even if the group strength is still too small and the expert’s leadership ability is neither pronounced nor desired by themselves.
Exactly for this there is now a solution: the system competence that is crucial for many companies is now getting more visibility. A systems engineer is becoming an attractive target for young, up-and-coming developers who are looking for an alternative to a line career. The competitive know-how of system and product architecture becomes a personal responsibility.
In the agile framework, it becomes possible to use the systems engineer as a multiplier for several project teams in parallel. This gives more teams better goals. This in turn strengthens personal responsibility in the team. In this way, he can grow out of the operational role bit by bit. A self-reinforcing effect!