Goals
- Clarify the work and responsibilities of the Product Owner
- Master the techniques of writing and prioritizing the stories of the product backlog
Program
The Scrum framework / Guide
Lifecycle of a Scrum project
Roles defined by Scrum: Product Owner, Scrum Master, Team
Time boxes: Sprint planning, Sprint Review, Sprint Retrospective, Daily Scrum
Artifacts: Product Backlog, Sprint Backlog, Burndown chart
Rules and key principles of Scrum
Responsibilities and role of the Product Owner
Activities of the Product Owner in the Scrum life cycle
Workshop: Analysis of the Scrum guide and passage of the Open Assessment PSPO I
Product vision: definition, interest
Form of a vision: Lean Canvas
Toolbox
Complete example of Product Vision Board
Workshop: Construction and analysis of a product vision
Bring out the need
Data collection techniques
Organization of the roles of actors (RACI)
Formalize the need: IEEE vs Use Cases vs User Stories
Workshops:
– Construction of a RACI matrix to organize the roles of a project.
– conduct of a collection interview (9-box technique)
– Animation of a brainstorming workshop and construction of mind maps.
Construction of a Roadmap
From objectives to functionalities: Impact mapping
Identify and structure the functionalities: Story mapping
Deduce the roadmap from the story map
Product backlog construction process
Writing user stories: form, INVEST specification
Complements of a user stories: constraints operational, models, ..
Writing acceptance tests (Behavior Driven Development method)
Test automation tools
Understanding technical debt: identification, categorization, prioritization
Workshops:
– Construction of an impact map from the product vision.
– Construction of a story map, identification of MMFs (Minimum Marketable Features).
– Construction of the roadmap.
– Writing user stories and three amigos workshops for acceptance tests.
– Organization of product construction (Ready Kanban)
– Product enrichment and optimization process.
Estimation techniques: ideal days vs story points
Implementation of the story points method
Reliability of the estimation
Factors for prioritization of needs
Prioritization methods: Kano vs MOSCOW vs Relative weights
Prioritization by themes: themes screening / scoring
Management of risks
Grouping and final order of stories in the product backlog
Workshops:
– Poker planning game for the estimation of stories.
– Calculation of the priority with the method of relative weights.
– Redesign of the product backlog.
Design:
– Scalable architecture
– Technical study work
Coding:
– Continuous integration
– Piloting by tests – Pair
programming
– Refactoring
– Acceptance tests
Maintenance:
– Bug management
Workshop: Panorama of the software toolbox of an agile project.
Different forms of an agile contract
Implementation of a Quality Assurance Plan (QAP)
Contracting by Sprint
Duration
2 days
Price
£ 1353
Audience
Anyone who must play the role of Product Owner in an agile Scrum project
Prerequisites
Knowledge of the agile Scrum method
Reference
Mé100116-F
Sessions
Contact us for more informations about session date