Determination of requirements

BPMN for Product Owners:

1. 4 views of processes: Process map, scenarios, control view, communication view.
2. Modelling decisions, concurrency and error handling
3. Conducting workshops with BPMN
4. From business processes to requirements

When developing or purchasing software, the business processes to be supported should actually play a central role. But if you look at a typical requirements catalogue for a software selection or a backlog full of user stories, you can hardly see the business processes. There is a gap between business processes and requirements. Used correctly, BPMN can help a product owner, for example, to design technically and technically coherent processes in coordination with the developers and to break them down into user stories.

Duration: 3 days of 8 hours each

Crash course for business analysts

1. The role of the BA

2. Determining functional requirements

3. Identifying non-functional requirements

4. Develop" and coordinate requirements

5. Manage requirements

In many companies, business analysts are a link between business and IT. Good business analysts act as catalysts. In practice, however, you often see the opposite - the "silent mail" effect. We teach the tools for requirements elicitation, which pitfalls to avoid and how requirements elicitation works in agile teams.

Duration: 5 days à 8 hours