Ketterä vaatimusmäärittely

Many organizations have adopted agile ways of working in their development teams and had a good experience with them. Many feel a need to expand their application from technical development to requirements specification activities and thus from IT to business.

In agile software development the requirements specification is a different matter than in waterfall projects. Specific methods are used that are not exactly the same thing as requirements specification in a traditional sense. One of these methods is called the user story method.

In CGI’s training you will learn what user stories are, how they are created and how they are used. After the training you will have a broader idea of agile software development and you will know how to use the INVEST model and story splitting techniques.

The training takes a much deeper approach on writing user stories than other agile trainings do. It is a good and practical addition to other courses, e.g. SAFe PO/PM, SAFe for Teams and well known Scrum courses.

Learning objectives:

After the course you can expect to know how to:

• Handle requirements in an agile software development way
• Write good user stories
• Split user stories into smaller ones

Who is the training for?

• Product owners and product managers
• Business stakeholders, experts and customer representatives in digital solution development programs
• Software developers, testers, IT experts, especially those who don’t have much experience in agile

Prerequisites

There are no actual prerequisites, but it is assumed that the attendees have earlier experience in being part of software, IT, or digital solutions development programs.