The user representative represents the users and their interests in the project, manages the unambiguous specialist solution requirements agreed with the specialist areas as a stable basis for implementation, and is responsible for the specialist success of the development. The user representative is the contact person for both the developers and the stakeholders, constituting a binding communication channel within the project organization. The user representative is appointed by the project sponsor and is managed by the project management, but is autonomous during solution development in specialist and solution-specific questions and decisions within the budget.

Under the agile approach, the user representative serves as an interface to the development team. In such cases, the role holder assumes specialist responsibility in the development team by additionally assuming the role of product owner, familiar in the agile environment. All detailed tasks and responsibilities in the agile development team are defined by the agile method used.

1. Responsibility for the solution
2. Establishment of all solution-specific requirements
3. Responsibility for the solution requirements
4. Maintaining transparency and making solution requirements available to all those involved in the project
5. Contributing the complete specialist requirements and functionality coordinated with the specialist areas and customers; representing stakeholder interests
6. Maximizing the added value of the development work (maximizing the value of the solution)
7. Ensuring the scope of goods/services and the specialist success of the solution
8. Involvement of stakeholders in solution development according to the stakeholder list
9. Compliance with ISDP requirements
10. Responsibility for communication with the development team (interface, agile )

1. Can access all required information
2. Decision on the characteristics of the solution including the quality requirements
3. Definition of the acceptance criteria
4. Collaboration with stakeholders and development team
5. Participation in defining requirements and concluding SLAs

1. In-depth knowledge of the specialist area
2. Knowledge of project management and of HERMES
3. In-depth knowledge of traditional and agile development management
4. Knowledge of the development management, design, and specification methods and practices
5. Basic knowledge of business administration
6. Knowledge of the project environment
7. Knowledge of the core organization's requirements in terms of operation of the application (e.g. for procurements, financing, controlling, security) or in terms of application of the project
8. Ability to establish, formulate, evaluate, and prioritize requirements and prepare change requests
9. Good writing skills
10. Abstraction and simplification ability
11. Ability to work in a team, to communicate, and to resolve conflicts
12. Visionary thinking
13. Assertiveness
14. Natural authority