Thursday, August 5, 2010

Scrum Product Owner Trainings (August --> December 2010)

Scrum Product Owner

Reference : SPO2010
Duration : 2 Days 

Price (VAT excl.) : 1.180,00 € 

Next Sessions : contact us




Duration (Days)


 26 – 27.08.2010




07 – 08.10.2010




02 – 03.12.2010




One of the critical Role in Scrum is the Product Owner. He/She sets the common objective that the Scrum team has to reach with him and acts as a link between the customer and the development. He/she prioritized the requirements and thus takes the responsibility that the most important (business-) issues are done first.

To this end he/she must understand how to deal with requirement management and release management practices "and how he/she prepared it in a Scrum hyper-productive context.

What you should learn! :

•           The role of the Product Owner in Scrum: no Scrum without a Product Owner.

•           Setting up effective Specifications: estimations, prioritizations, Value Driven Workshops

•           Building a clear Vision

•           Setting up a Release Strategy

•           Building a powerful Product Backlog

•           Keeping quality standards at the highest level with the DEFINITION OF DONE

•           Tools, techniques and real-life feed back

 Teaching Method :

40% practices

Training like coaching approach.

Audience :

PMO, Functional Managers, Project Manager, Team Leaders, IT Managers, Product Managers, Business Analysts

Pre-requisites :

Having an agile management background is a plus

Have read the Scrum Guide


o    Agile concept and Values

  • Agile Manifesto’s principles
  • Empirical Project Management
  • The 3 Scrum legs

o    Scrum

o    The Scrum Process

o    RULES



o    Scrum Roles

o    DoD : Definition of Done

o    Product Owner Role and Responsibilities

  • At Customer’s level
  • At User’s level
  • At Management’s level
  • At Scrum Team’s level
  • Product Owner’s characteristics

o    Project Chartering

  • Customer’s needs
  • Product attributes
  • Benefits
  • Desirable qualities
  • Vision Scope
  • Determine Timeframe and budget

o    User Stories

  • User Stories on the Product Backlog
  • User Roles
  • User Story Card
  • Good Stories are Invest
  • The 3 C Criteria
  • Non-Functional Requirements

o    The Product Backlog

  • Building a Product Backlog
  • Prioritization’s factors
  • Stocking, shaping and grooming the Backlog
  • The DEEP approach
  • Product Roadmap

o    Sprints

  • Sprint Workflow and Characteristics
  • Sprint Estimating and Planning
  • Daily Scrum (see part 9)
  • Sprint Review and Retrospective
  • Sprint Reporting
  • Definition of Done vs Level of Done at Sprint

o    Release Planning

  • Estimate Product Backlog Items
  • Estimating with Story Points
  • Velocity
  • Release Strategy
  • Release metrics
  • Release Planning Steps

o    Tracking Progress

  • Burndown Charts
  • Velocity
  • Time-to-market
  • Return of Investment and Earned Value
  • Reporting Tools

o    Distributed Teams

  • The laws: Brook’s law, Jidoka, organic Growth, Conway’s law
  • Perils of collocated and distributed teams
  • Agile models: Scrum-of-scrums, Meta Scrum, Agile Governance, [sKale]

Posted via email from pierreneis's posterous

1 comment:

  1. Bonjour, je vous réponds sur votre blog, fonctionnant au minimum budget sur viadeo je n'ai la possibilité que d'envoyer des messages à tous.
    Donc pour aristote, gestion comptable de la sncf, je participais por Dataid à la définition et à la mise en test des requêtes avec Focus. je suivais aristote extérieur à KPMG qui en avait la maitriseet j'ai recueilli ls compte-rendus à l'époque.
    Quel point voulez vous que j'explicite?