agile scrum

Goals


- Master the management of agile projects with the Scrum method

Program

Project management: predictive vs agile
Why agility?
The agile manifesto
Overview of agile methods
Approach to adopting agility

Lean Management: objective,
Kanban principles : principle, advantage, life cycle of a label
XP Practices (eXtreme Programming)

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 / role
Choice of the size of the sprint
Constitution of the team
Weaknesses of the methods

Workshop: analysis of the Scrum guide and passage of the Open Assessment PSM 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 of acceptance tests (Behavior Driven Development method)
Test automation tools

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.

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.

Roadmap and release plan
Sprint planning meeting, construction of the sprint backlog
Daily Scrum meeting
Performance indicators: Burn Down and Burn Up chart
Progress monitoring: Kanban board, Parking Lots
Sprint review Sprint
retrospective

Workshops:
– Animation of a sprint planning meeting, division of stories into tasks.
– Sprint review: actors, demonstration, validation of stories.
– The art of retrospective. – Use of agile project management tools.

Different forms of an agile contract
Implementation of a Quality Assurance Plan (QAP)
Contracting by Sprint

Duration

3 days

Price

£ 1851

Audience

Anyone to be involved in a Scrum project: ScrumMaster, Product Owner, Scrum Developer, DSI

Prerequisites

Project management concepts

Reference

Mé100115-F

  

Sessions

Contact us for more informations about session date