Skip to main content

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

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

Mirek has great knowledge on topics that he is teaching. Trainings are well prepared both in materials and real life examples. If you have possibility (...)

Maciej Mordaka
Maciej Mordaka ★ PMP, PRINCE2, P3O, ITIL, PSM-I

Mirek has turned out to be a most creative, collaborative, inquisitive, challenging, humourous, proactive, quick and agile ambassador of the ASL BiSL (...)

Miroslaw Dabrowski is absolutely great at what he does. He does an excellent job of coaching and helping you to see how your project can be done in (...)

Maciej Kordała
Maciej Kordala ★ PRINCE2

I had a pleasure to attend "Architect Enterprise Applications with Java EE" conducted by Mirosław. Mirosław has a very deep knowledge about Web Tier, (...)

Karol Hadała
Karol Hadała ★ PSM-I, SCJP 5.0

Byłam uczestniczką szkolenia PRINCE2 Foundation prowadzonego przez Mirka. Mimo, że metodyka PRINCE2 obejmuje szeroki zakres materiału, Mirek potrafił (...)

Great instructor with deep knowledge about Java and UML. As far as I remember all questions were answered, even those which were not fully in scope of (...)

Grzegorz Szczepanski
Grzegorz Szczepanski ★ PMP, PRINCE2, SCJP, ITIL Intermediate

I have met Miroslaw, when I took mine Prince2 foundational training and exam. He is the kind of trainer who has professional credentials and (...)

Mirek jest jedną z najbardziej inspirujących osób, jakie miałem okazję spotkać w życiu. Jest niezwykle pomocny, obdarzony dużą empatią i skupiony na (...)

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!