Room
Track 1
Audience
Manager, Product Owner, Project Leads
Key-Learnings
- What contribution does initial requirements engineering make before the start of a project, regardless of whether it is agile or traditional
- What content should an initial requirements workshop contain?
- Which creativity techniques can be used to get an initial inventory of the requirements
How an initial requirements workshop can ensure a successful project no matter if your setup is traditional or agile
Most of us have already been part of projects that have turned out very differently than we initially thought. Suddenly the team is wrongly staffed, the budget or time is insufficient, or the scope was misjudged. Here it no longer matters whether the project follows an agile or a traditional setup.
How can we ensure that the risk of these situations occurring is minimized? The cornerstone for successful projects is laid before the actual start. In addition to clarifying the framework conditions, knowledge of the requirements for the system to be developed is crucial for a successful start to the project.
In this talk, I will explain the concept of our requirements workshop and take a closer look at the individual sections for an initial inventory of the requirements. Because the goal is to know as much as possible about the upcoming challenges before the project even starts. This way managers will be able to make the right decisions i.a. the regarding team size or the technology used and Product Owners can begin to prioritize requirements, set up milestones and define their MVP early.