Course Outline
1. "Scrum framework" – a concise overview of project organization and working with business value.
- Managing requirements in Scrum – the Product Backlog Refinement process
- Scrum artifacts: Product Backlog – the requirements register, Sprint Backlog – the task register, Increment – a functional piece of business value
- User Story Map – an approach for structuring requirements effectively
2. Demonstration of a sample requirements process within an application – "from capturing customer needs through creating a vision, Product Backlog, and Sprint Backlog, using a project to implement an application supporting the customer's selected business processes as an example".
3. Identifying project target groups – personalizing stakeholders
- Stakeholders, the project client, and end users
- The multigenerational factor and its influence on identifying customer needs
- Workshop: designing requirements for project users – defining project personas within a multigenerational market context
4. Formulating the product/project vision
- Project goal and vision
- Workshop: creating a product/project vision – using the Canvas model as a foundation for delivering business value based on the customer's needs and situational context
5. Defining project quality – the Definition of Done
- Identifying project quality criteria
- Workshop: creating a definition of project quality – the Definition of Done
6. Identifying business value in the project – working with the Requirements Register (Product Backlog)
- Organizing work with the Product Backlog – translating customer needs into high-level and low-level requirements
- Integrated Product Backlog – common requirements and domain-specific requirements
- Workshop:
o Preparing a requirements registry – epics, themes, user stories
o Product Backlog within process and product approaches
o Release planning – the project roadmap
7. Identifying business value in the project – requirements and acceptance criteria – building a User Story Map
- Identification, definition, decomposition, and prioritization of requirements – tools and techniques such as those by Richard Lawrence and the Elephant Carpaccio exercise
- Workshop:
o Defining requirements – capturing requirements using the user story formula
o Measuring requirements and accounting for effectiveness – defining acceptance criteria for user stories
o Prioritizing requirements based on the project customer’s needs
o Transferring requirements – ensuring mutual understanding by translating customer needs into transparent user stories
8. Accounting for business value
- Requirements, tasks, presenting business value, and enhancing efficiency
- Workshop:
o Decomposing requirements into tasks
o Simulating a team presentation of requirements and deliverables
9. Refinement – summarizing the workshop as an "action plan"
- Workshop: summarizing the training using the SSC formula with facilitation techniques
o Start – new good practices I will implement
o Stop – activities I will discontinue
o Continue – practices I will keep applying
Requirements
No prior preparation is required for this training.
Testimonials (1)
Understanding that in project management is more about tailoring and assessing each situation than just deciding what to do next.
