Product BACKLOG is 'known' always – it is INSPECTED at Sprint Review & ADAPTED (this is EMPIRICISM)

--------

Scrum is based on empiricism and Lean-thinking. Empiricism implies that, when making decisions, we are based on what we know – on our experience and actual observations.

"OK, but what does it look like in real work?” For example, usually, there are enough elements in the Product Backlog for the team to work on for at least the next few sprints. However, at the Sprint Review, the Scrum Team and Stakeholders collaborate on what to do next, and the Product Backlog may also be adjusted – this is “Making decisions based on what is known now”.

--------

In this online course, you will learn about the most popular Agile approach used by 87% of teams – Scrum! As an Agile coach and Scrum Master with years of experience, Dim Blinov will guide you through the essential elements of Scrum including roles, events, artifacts, values, and pillars.

The course covers various elements of Scrum, including:

1. The definition of Scrum. It is a lightweight framework that helps teams and organizations generate value through adaptive solutions for complex problems.

2. The key elements of Scrum, including the accountabilities (Product Owner, Developers, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment) + the commitments associated with the Scrum artifacts (Product Goal, Sprint Goal, Definition of Done).

3. The five Scrum values (Focus, Openness, Respect, Commitment, and Courage) and the three empirical pillars (Transparency, Inspection, and Adaptation).

4. Additional elements of Scrum, such as Product Backlog Refinement, Empowerment and Self-management, Lean thinking, Cross-functionality, and Iterative-Incremental approach.

To dig deeper, the course will explain to you:
– The role of the Product Owner in defining the Product Backlog and Product Goal.
– The role of the Developers in creating a usable increment each Sprint.
– The role of the Scrum Master in facilitating the Scrum process and causing the removal of impediments.
– The benefits of Sprint as a container for all Scrum events and activities.
– The various Scrum events and how they support transparency, inspection, and adaptation.
– The importance of continuous improvement and how the Sprint Retrospective supports this.
– The relationship between Scrum and delivering value to the customer through the product.