The focus in requirements engineering is naturally on eliciting, documenting, checking, agreeing and managing requirements. Clear communication with sufficient sensitivity for the respective counterpart, and the ability to adjust to this, are fundamentally important for successful requirements engineering. This is complemented by a very structured and systematic way of working in order to successfully perform requirements engineering.

In the role of requirements engineer, our consultants undertake the following activities, among others:

•     Use of elicitation techniques, e.g. interviews, workshops
•     Use of videos to elicit, communicate and document requirements
•     Use of different documentation techniques or business process descriptions
•     Structuring of requirements
•     Preparation and implementation of requirements for different roles
•     Use of various tools
•     Creation of a specification
•     Review and translation of a requirements specification
•     Stakeholder analysis
•     Review and restructuring of a requirements specification

In systems engineering, one considers a product, both as a complete system and over the entire product life cycle, from the idea to disposal.

The main activities in systems engineering take place during development. In this context, requirements that will become necessary for the entire product life cycle are already taken into account during development. These are, for example, requirements from logistics, production, quality assurance, further development, care, maintenance or disposal.

In addition to good facilitation skills, systems engineers have sufficient knowledge to assess individual decisions at the component level. They ensure that all product requirements are implemented.

In the role of Systems Engineer, our consultants perform the following activities, among others:

•     Eliciting and consolidating requirements
•     Use of elicitation techniques, e.g. interviews, workshops
•     Documentation of requirements
•     Documentation of system architecture with UML or SysML
•     Use of different documentation techniques or process descriptions
•     Managing requirements
•     Structuring of requirements
•     Preparation and implementation of requirements for different roles
•     Consistent changes of requirements
•     Use of various tools
•     Creation of a specification
•     Review and translation of a requirements specification
•     Maintenance of a requirements document
•     Stakeholder analysis
•     Review and restructuring of a requirements specification

The business analyst is responsible for performing the selected business analysis tasks, providing an intermediary role between development and stakeholders. That is, he uses methods and techniques used in collaboration with various stakeholders to understand the business policies, structures and operations in an organization and propose solutions/improvements that will enable the company to achieve their goals in order to survive in the market.

In the role of business analyst, our consultants undertake the following activities, among others:

•     Identifying the improvement potential of an organization
•     Preparation of business cases and their presentation
•     Determination of solution variants
•     Detailing the selected solution (requirements)
•     Handing over the requirements to the development team

A team analyst supports a Scrum team in analyzing new requirements and documenting the system to be developed. He brings the necessary requirements engineering know-how to your project in order to have the functional requirements penetrated and documented at the right level of detail at the right time.

In the role of team analyst, our consultants perform the following activities, among others:

•     Supporting the product owner in describing the product backlog items
•     Supporting the product owner in the analysis and evaluation of functional requirements
•     Developing functional solution concepts in cooperation with the product owner
•     Creation and maintenance of functional and technical documentation

A Scrum Master focuses on the sustainable optimization of team performance. This can be done by improving the understanding of agile principles, by resolving internal or cross-team conflicts, by optimizing the working environment or by further developing individual team members. The Scrum Master recognizes potential for improvement and manages to raise it.

In the role of the Scrum Master, our consultants take on the following activities, among others:

•     Preparation, moderation and follow-up of team ceremonies
•     Supporting the Scrum team in the continuous development of their own skills and capabilities
•     Solving impediments for the Scrum team
•     Coaching of the Scrum team in the implementation of the agile principles and values
•     Moderation of conflicts within the team or between the teams

A product owner plays a central role in an agile development environment and takes on many of the classic requirement engineering activities, such as eliciting, prioritizing and coordinating requirements. As a good product owner should have internalized the agile values as well as have a sound methodological knowledge, our consultants are predestined for this role.

In the role of Product Owner, our consultants take on the following activities, among others:

•     Determination and coordination of the requirements with the representatives of the business unit
•     Creation of items and maintenance of the product backlog
•     Prioritization of requirements in the product backlog
•     Handing over the requirements to the development team
•     Creation of release roadmaps and coordination of these within the organization