Do you want to write great requirements quickly? Do you want to see real examples of great requirements on a typical backlog? Do you wish there was a straightforward way to turn customer wants and needs into something that can be build?

If you’ve answered yes to any of the above then this course is ideal for you. Requirements can be a detailed subject, taking many years and lots of experience to master, but there reality is that by following a few key principles, you can learn to write great requirements quickly. This course is the ideal place when you’re starting out with requirements.

This course has been created to help you become a pro at writing requirements in only 118 minutes.   Whether you’re a Product Owner, Business Analyst or simply someone who needs to capture needs and write them as clear requirements.

There are dozens of hours you could spend learning about writing perfect requirements, but the truth is that with a few fundamental skills and knowledge, you can quickly write clear and effective requirements, without the need to spend 20+ hours studying.

The course provides everything you need to write great requirements, in 3 key parts:

1) The environment requirements are written in - you can’t write great requirements if you don’t understand who there’re for and where you get them from

2) Fundamentals of a great requirement - A simple set of core principles, covering the User Story format and Acceptance Critera styles

3) Mock project where we gather requirements and write them together on a real product backlog

We will cover:

Roles involved in writing Requirements

- Why we write requirements

- Who writes requirements

- Who needs Requirements

Where Requirements fit in Agile

- Product Backlog

- Sprints and Sprint Backlog

- Estimation

- EPICS, Features and User Stories

Fundamentals of Great Requirements

- Examples of high quality requirements

- Acceptance Critera Styles

- Principles of Great Requirements

Creating Requirements in a  real backlog management tool

- Storymapping

- Creating our Requirements Hierarchy

- Creating Links and Dependancies