Description

This course, based on practical exercises and examples, will allow you to analyze the situations experienced in the implementation of the Scrum method and to emphasize good practices. The different roles involved in Scrum will find concrete answers to the difficulties encountered.

Who is this training for ?

For whom ?

Scrum Master, Product Owner, developer, tester, any actor involved in an Agile mode project.

Prerequisites

Training objectives

Understand the roles and artifacts of the Scrum method

Clarify an expression of needs and define a "business value"

Define user stories and build a realistic product backlog

Improve in the daily management of the sprint

Train on agile planning situations

Equip yourself with tools and best practices to better estimate loads, and monitor the progress of the project in Scrum

Training program

• Reminders on Scrum and Agility
  • Agility, another vision.
  • Roles and artifacts.
  • Meetings called "ceremonies".
  • Complementary contributions (Lean, XP.
  • ).
  • Collective reflection Exchange and sharing of experiences.
• The activities of the Product Owner
  • Clarify the expression of needs.
  • Plan based on business value.
  • Accept or reject the product.
  • Study case study Analysis of the Product Owner's activities.
• Organization and collaboration in a Sprint
  • Iteration planning.
  • Frozen content, change.
  • Prepare well and lead the Scrum Meeting so that it is effective.
  • Management of iteration by Kanban.
  • Review of self-organization, role of the Scrum Master.
  • Developments aligned with technologies rather than cases of use: task-story difference.
  • Presence of the functional representative, demonstration at the end of iteration.
  • Role of the Product Owner.
  • Improve the retrospective , make better use of sprint debriefs.
  • Scenario Exercises on several cases of anti-patterns observed.
• Agile planning
  • The four levels (roadmap, version plan, .
  • ).
  • Basic principles.
  • Of the infernal triangle squarely virtuous.
  • Implement a viable rhythm for all.
  • How to react if the prioritization of User Stories does not take into account development constraints? Implementation situation Planning Game between Product Owner and Developer roles.
• Other advanced points
  • Effort points vs H/J.
  • Planning Poker, estimation by similarity.
  • Estimate stories and features.
  • Tools for expressing needs, planning and visual management.
  • Reporting: Burndown, Burnup Charts, other indicators.
  • The application does not pass the tests.
  • Organization to fix bugs (Stop the line).
  • The four rules of simple design.
  • Test Driven Development.
  • Implementation situation Agile tools and practices.