Skip to main content

About

The two-day training for Product Owners is designed to equip participants with the skills necessary to fulfil the role of a Product Owner – a business-minded entrepreneur, responsible for the product vision and the Product Goal, collaborating closely with other members of the Scrum Team(s).

The training takes participants through the process of defining a product, covering aspects such as creating a product vision, establishing a roadmap, identifying business drivers, and understanding the needs of customers and users through the formulation of Product Backlog Items (ofter User Stories, a common practice in agile). Attendees will acquire the knowledge and skills necessary to effectively construct and manage the Product Backlog.

  • Length: 2 days
  • Level: Foundation
  • Form: 50% lectures / 50% workshops
  • Registration: Training on demand for groups
  • Logistics: At the customer’s premises (on-site) or anywhere else (online)

Agenda

  • Introduction to Agile (in-depth understanding of the Agile Manifesto)
  • Agile and the traditional approach (sequential cascade)
  • Theoretical foundations of Scrum
  • The three pillars of Scrum
  • Understanding the differences between project management and product management
  • Overview of Scrum elements (Rules, Roles, Artifacts, Events)
  • Product Owner – who is he and what is his role in the team
  • Technical vs Business Product Owner
  • Good Product Owner features
  • Product management in Agile
  • Valuation of product features, value proposition
  • Ways to measure the value delivered
  • Value provided and costs
  • Product Backlog and requirements management
  • Setting priorities
  • Estimates
  • Planning and monitoring the progress of work in Scrum
  • Scaling in Scrum
  • Product Owner’s work tools
  • Scrum patterns and anti-patterns
  • Preparation for the PSPO I exam

Participants

  • Future and current Product Owners
  • Agile team clients
  • Project / product sponsors
  • Middle and senior staff
  • Members of Scrum teams
  • PMO, specialists and managers supervising projects
  • Suppliers whose clients want to switch to an agile project management model
  • Everyone interested in learning the differences between three popular approaches: PRINCE2, PRINCE2 Agile, SAFe, DAD, LeSS, DSDM and Scrum (the trainer is an experienced Agile Coach, certified in these areas)
  • Everyone interested in using Scrum in practice
  • Everyone interested in thorough preparation for the Professional Scrum Product Owner I exam (PSPO I)

Learning Goals

The Scrum process

The Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose.
The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done”.
The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised.

Testimonials

Great trainer with wide knowledge not only in the area that was the subject. Has extended the subject of training especially for the needs of the (...)

Paweł Kulpa
Paweł Kulpa ★ AgilePM

Miroslaw conducted a great training in line with motivating atmosphere. Very customer oriented with deep knowledge of theory as well as practical (...)

Mirosław is a great speaker with deep knowledge background in Agile PM and big bag of experience. During presentation Mirosław was sharing high level (...)

Świetnie przeprowadzony warsztat z Narzędzi i Technik w Zarządzaniu Projektami. Profesjonalnie ale jednocześnie zabawnie. Najlepszy coach jakiego (...)

Miałem przyjemność uczestniczyć w szkoleniu prowadzonym przez Mirka. Przeprowadzone szkolenie stało na bardzo wysokim poziomie merytorycznym i było (...)

Robert Uszyński
Robert Uszyński

I had a reall pleasure to participate in P2A workshops that Mirek prepared for our local PMI branch. Very valueable and inspiring experience Agile (...)

Miałam okazję brać udział w szkoleniu prowadzonym przez Mirosława Dąbrowskiego dot. Scruma, przygotowujące do certyfikacji na Product Ownera. (...)

Byłam na wykładach Mirka. Człowiek z niesamowitą energią, charyzmą, pełen poczucia humoru. Potrafi niesamowicie zaciekawić swoimi zajęciami. (...)

I had big pleasure to work and cooperate with Mirosław in one of my projects in Roche company. He is very experienced and has very practical approach. (...)

Supporting resources

Scrum Guide [2020.11]

Scrum Guide 2020
www.scrumguides.org [11.2020]

Scrum Guide 2017

Scrum Guide 2017
www.scrumguides.org [11.2017]

The Scrum Papers - Nuts, Bolts,
and Origins of an Agile Process
DRAFT [2007.10.14]

Evidence-Based Management Guide
by Scrum.org [09.2020]

Evidence Based Management Guide [2019.01]

Evidence-Based Management Guide
by Scrum.org [01.2019]

Evidence Based Management Guide [2018.09]

Evidence-Based Management Guide
by Scrum.org [09.2018]

The 8 Stances of a Scrum Master Whitepaper v2.0 [2017.05]

The 8 Stances of a Scrum Master
Whitepaper by Scrum.org [05.2017]

Scrum Master Trends 2019 by Scrum.org

Scrum Master Trends Report
by Scrum.org [2019]

Subscribe To Our Newsletter

Subscribe To Our Newsletter

Join our mailing list to receive the latest news and updates from our team.

GDPR EN

You have Successfully Subscribed!