Scrum Master - Enterprise Agile Coaching

About

Scrum adheres to a defined time frame, known as a Sprint, for both planning and delivery. The success of this framework (not methodology) hinges on the discipline, habits, organizational culture, and collaborative efforts of the team.

The Scrum Master assumes multiple roles as a coach, mentor, trainer, and facilitator. Their responsibility is to encourage adherence to Scrum values without imposing them and to disseminate Agile principles throughout the organization. By helping eliminate obstacles and fostering continual improvement in team maturity and value-related processes, the Scrum Master plays a crucial role.

In the Scrum framework, stakeholders collaborate closely with the Scrum team, particularly with the Product Owner, who oversees the overall product vision and the Product Goal. The short Sprint periods enable the team to promptly respond to market needs, competitor activities, and emerging trends. Frequent releases within each iteration facilitate rapid validation of assumptions against user expectations and satisfaction levels. This iterative process results in a product closely aligned with user needs, contributing to the ongoing development of the Scrum Team and its business success.

Professional Scrum Master training equips participants to take on the role of a Scrum Master, responsible for overseeing the Scrum process and ensuring that the team improves their maturity over time.

Length: 2 days
Level: Foundation
Form: 50% lectures / 50% workshops
Enrolment: 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
Scrum theory and basics
Overview of Scrum elements (Rules, Roles, Artefacts, Events)
People, Teams, teams self-organization.
Scrum Master – who is he and what is his role in the team
Product management in Agile
Product development management through value
Ways to measure the value delivered
Value provided and costs
Product Backlog and requirements management
Setting priorities
Estimation
Planning and monitoring the progress of work at Scrum
Scaling in Scrum
Scrum Master work tools
Preparation for the PSM exam

Participants

Future and present Scrum Masters
Team leaders
Members of Scrum teams
Project managers preparing for the role of Scrum Master
Managers and members of project 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 Master I exam (PSM 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

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

I attended AgilePM course led by Mirek. He is an excellent coach with great interpersonal skills.His passion and positive energy give a lot of (...)

Aleksandra Gałązka ★ AgilePM

Consultant for IT systems at TAURON Obsługa Klienta

Mirek szkolił mnie do egzaminu AgilePM. Powiem tak, nie tylko wiedza przydała się na egzaminie, ale również w pracy IT Project Managera.

Marta Markiewicz ★ PMP, AgilePM

IT Project Manger at Bank BPH

I got opportunity to interact with Mirek on M_o_R training. He is a great trainer with knowledge not only in the area that was the subject. His (...)

Małgorzata Kral-Żeglarska ★ M_o_R

Rocket Studio sp. z o.o.

Miałem przyjemność uczestniczenia w szkoleniu M_o_R prowadzonego przez Mirka. Jego zaangażowanie i nietuzinkowy sposób prowadzenia szkolenia pozwolił (...)

Marek Zasłona ★ M_o_R

p.o. Naczelnika Wydziału Informatyzacji w IPN

Miałem ogromną przyjemność uczestniczyć w kursie agile/scrum prowadzonym przez Mirosława. Ogromny zastrzyk wiedzy, warsztatowe, bardzo pragmatyczne (...)

Cezary Goral

R&D managing engineer in Zieta Studio

Obszerny materiał PRINCE2 został przedstawiony przez Mirka w ciekawej formie, w krótkim czasie trzydniowego szkolenia. Pomaga poukładać wiedzę, nie (...)

Michal Wojtalewicz ★ PRINCE2

Software Developer w Cognitran

I recommend Miroslaw Dabrowski as a great and competent professional trainer. He is very experienced and has very practical approach. Moreover, (...)

Daniel Jastrun

Partner at Maruta Wachta sp. j.

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