Do you have a problem with a first solution idea and would like a time and cost indication for it? Which functions provide the most added value? What are the user groups? What are the system boundaries?
Professional requirements engineering is also, or especially in agilely managed projects, the indispensable compass for initial planning and orientation in the course of the project. With our powerful and well-thought-out models, we ensure that the software solution gets off to a planned start and can be consistently developed towards the project goals set.
Requirements artifacts in an agile environment
Requirements capturing
- Workshops with experts
- Definition of project objectives
- Identification of user groups and use cases
Modeling
- Business processes
- Domain models
- System context
Initial project description
- Setting up the initial product backlog
- Story map with epics and user stories
- Retaining non-functional requirements (NFRs)
Project
- Release Plan and Product Roadmap
- Cost indication
How we proceed
In the early phase of a complex IT project or when large volumes are to be added to an existing system, there are often individual ideas and wishes that are not yet mature; in the best case a vision of the finished software solution. Before the implementation can start, a merging of these fragments into a coherent concept is necessary.
This is where our requirements engineering starts. With our expertise from a variety of digitization projects, we think strongly results-oriented. As moderators, technology experts and conceptualists, we are at your side. Together, we set the course for a successful IT project.
After the validation of product vision and project objectives, we develop the technical requirements from the point of view of the different user groups in a workshop series with the identified stakeholders. For each relevant use case, the business processes and the desired system behavior are analyzed and adhered to.
The so-called non-functional requirements, which specify technical boundary conditions and quality criteria, such as access times or reliability are not neglected.
You benefit not only from our professional expertise, but also from our proven methodology in order to obtain a professional and recognized result. Conclusively documented project requirements based on jointly developed application scenarios are the necessary basis for the following software development. For example, the document artifacts created using established techniques (UML, BPML, etc.) clearly show how the terms of the subject domain are related and where the limits of the system to be developed lie.
Based on requirements capturing and modeling, we create an initial product-backlog as a starting point for development, whereby the user stories are grouped thematically and prioritized timewise using a story map. Subsequent release planning then forms the basis for a sound cost indication.
The XITASO Difference
The technical depth first – the implementation details later
The importance of the concepts and models that arise in requirements engineering lies in the creation of a common professional understanding between all project participants. That’s why we consciously go broad and develop the requirements right from the start, together with our technology and method experts and the specialist experts from the customer’s side. This exchange forms the basis for the fact that the multitude of necessary detailed decisions in the implementation phase can be made largely independently by the development team.
Your added value
- Creating a common understanding
- Clear definition of requirements
- Analysis and evaluation of use cases
- Summary documentation of the project (e.g. for tenders)
- Roadmap for successful implementation
In our requirements engineering, we work with you to develop a solution concept and an implementation plan. Often, initial approaches to usability and design of the graphical user interfaces are also useful.