Workshop: How to write requirements [WREQ]

OVERVIEW

Do you work as a Business Analyst or do you have a role in the organisation where you are expected to write requirements? We all know how important it is to correctly articulate the needs of users, end-users and the customer (business) and to document these in such a way that all relevant parties (stakeholders) can find the requirements drafted and understand what the requirements mean.

Based on research and hard data, it has been established that not capturing the right requirements correctly formulated contributes to a project or product development not being successful, even though we met the deadline and stayed within budget.

How do I write good requirements, how do I know they are written correctly. Do the stakeholders understand what is written and does the requirement really express the needs of the stakeholder?

During this two-day workshop we will discuss writing correct requirements in the traditional way with many exercises. Which words can I use and which not? What do I have to pay attention to? What agreements do we make within the organisation?  The workshop consists of a number of modules in which we go a step further into the subject matter, all supported by many exercises.

From the traditional way of writing, we take the step to writing User Stories, based on identified Users/Users (User groups). We will pay attention to the level of detail in a User Story.

AUDIENCE

Deze training is voor iedereen die met requirements te maken krijgt:

• Business Analisten
• Product managers
• Project managers
• Product owners,
• en ook zeker andere stakeholders

CERTIFICATION

CONTENT

During the first day, we discuss the meaning of requirements, which types we distinguish and why this distinction is important. We think about how we can set up and structure requirements as efficiently and effectively as possible so that we can properly follow the lifecycle of a requirement. We start right away with assessing and writing requirements.

On the second day, we continue with what agreements we need to make in order to write the right requirements correctly, and we also make the step to using User Stories.

Day 1:

Introduction

What are requirements?            

Which types of requirements do we know,
Which templates we can use.
What is the need for requirments.
What are attributes

which type of attributes do we know
what is the necessity of attributes

Module 1:

Overarching aspects
Exercises
Per aspect max. 5 exercises
Per module multiple choice exercise, and rewrite actions.

Module 2:

Focused aspects
Exercises
Per aspect max. 5 exercises
Per module multiple choice exercise, and re-write actions.

Module 3:

On semantics (language) level - which words to use
Exercises
Per aspect max. 5 exercises
Per module multiple choice exercise, and rewrite actions.

Day 2:

Short review

Module 4:

On semantics level - continuation
Exercises
Per aspect max. 5 exercises
Per module multiple choice exercise, and rewrite actions.

Module 5:

Semantic level, overarching and psychological
Exercises
Per aspect max. 5 exercises
Per module multiple choice exercise, and re-write actions.

Module 6:

Tips and tricks - Models, Reviews, techniques (which ones in High Level)
User Stories - splits, models, approach...