Product Owner - Enterprise Agile Coaching

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

Brałem udział w szkoleniu prowadzonym przez Mirosława. W skrócie: świetny poziom merytoryczny, bardzo dobre przygotowanie, umiejętność przekazania (...)

Szymon Długokęcki

Senior Software Developer at Nearshoring Solutions

Szkolenia prowadzone przez Mirka są w pełni profesjonalne, interesujące i bardzo praktyczne. Przygotowane przez niego materiały dodatkowe oraz liczne (...)

Paulina Lisowska ★ PRINCE2

PMO at BZ WBK Bank

Mirosław has a great attitude and passion for conducting trainings. As a participant, I can say that it is not easy to get bored during the training (...)

Michał Wargacki ★ AgilePM Practitioner

Development Team Leader at EPAM Systems

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. (...)

Michał Papież

🔎 Agile Coach & AI Enthusiast💻

Miałem przyjemność uczestniczyć w szkoleniu M_o_R, które prowadził Mirek. Jeszcze nigdy nie trafił mi się tak proaktywny i zaangażowany prowadzący. (...)

Grzegorz Mazur ★ PRINCE2 Practitioner, MSP, M_o_R

Bureau Director, Business Solutions at Deutsche Bank Polska

Miroslaw is very open-minded, highly skilled IT instructor. His experience with programming and design of IT solutions is extremely useful when (...)

Marcin Mleczko

Solutions Architect at Mastercard Processing

I was very impressed with Mirek's extended knowledge of... everything! 🙂 Huge passion for both learning and teaching. I was very satisfied with the (...)

Anna Wojciechowska

Senior Project Manager at QLOC S.A.

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