User story map in practice - defining business value

The training requires no additional preparation.

The training allows you to learn in practice the aspects of preparation of business requirements based on the approach
user story map approach. The basis of the training is the process of working with requirements - from identifying customer needs transferring needs to the preparation of an effective Product Backlog and decomposition of requirements based on the User Story Map approach.

The training is dedicated to people interested in developing competence in defining business value, quality and effective design of
business requirements.
The training consists of a content part, workshops, practical examples.

1. "Scrum framework" - organizing the project and working with the business value "in a nutshell".

• organization of work with requirements in Scrum - Product Backlog Refinement process
• artifacts in Scrum: Product Backlog - a register of requirements, Sprint Backlog - a register of tasks, Increment - a working business value
• User Story Map - an approach to effectively build requirements

2. Presentation of a sample process of working with requirements in an application - "from registration of customer needs through creation of vision, Product Backlog, Sprint Backlog on the example of a project to implement an application supporting selected customer's business processes". 
3. Identification of project target groups - personalization of stakeholders

• stakeholders, project client and end users
• multi-generational and impact on identifying the needs of customers
• workshop: designing requirements for users project - defining project personas in the context of the multigenerational market

4. Formulating the product/project vision

• project goal and vision
• workshop: creating a product/project vision - Canvas model as a basis for delivering business value based on the needs and context of the situation at the customer

5. Defining project quality - Definition of Done

• Identifying project quality criteria
• Workshop: creating a definition of project quality - Definition of done

6. Identifying the business value in the project - working with the Requirements register (Product Backlog)

• organization of work with Product Backlog - transfer of customer needs into high and low level requirements
• Product Backlog integrated - common requirements and requirements for "domains"
• workshop:

o preparing a requirements registry - epic, theme, user story
o product backlog in process and product approach
o release planning - project road map

7. Identification of business value in the project - requirements and acceptance criteria - creating User Story Map

• identification, definition, decomposition and prioritization of requirements - tools and techniques such as: Richard Lawrens, Elephant carpaccio exercise
• workshop:

o defining requirements - identifying requirements in the user story formula
o measuring requirements and accounting effectiveness - identification of criteria acceptance criteria for user story
o prioritization of requirements based on the needs of the project customer
o requirements transfer - how to ensure that we understood - transferring customer needs into transparent user story

8. Accounting for business value

• requirements, tasks, presenting business value and increasing efficiency
• workshop:

o decomposition of requirements into tasks
o simulation of presentation of requirements and deliverables by team

9. Refinement - summary of the workshop in the form of an "action plan"

• workshop: summary of the training in the SSC formula using facilitation techniques

o Start - what I will implement as a new good practice
o Stop - what I will stop
o Continue - what I will continue to apply