Scrum-Theory

Scrum Theory

Scrum-Theory

Scrum Theory

Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known at the time. Scrum employs an iterative, incremental approach to optimise predictability and control risk.

Three pillars uphold every implementation of empirical process control: Transparency, Inspection, and Adaptation.

Transparency

Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen.

A common language referring to the process must be shared by all participants and those performing the work and those inspecting the resulting increment must share a common definition of “Done” We will come onto this and how important it is in a later series.

Inspection

Scrum users must frequently inspect Scrum Artefacts to find any issues or blocks in the road they can then and adjust so the teams stays on track to delivering the Sprint goal.

Their inspection should not be so frequent that inspection gets in the way of the work, again later in the series we will go into specific details about timings and when best to run your Scrum events. To get the most out of these events, it is beneficial that the team is guided by a professional in the scrum field. However please keep in mind the development team must feel comfortable to talk openly and honestly to get the best out of them.

Adaptation

If someone that is performing the above inspection determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted as mentioned above we always want focus on the successful delivery of the Sprint but not reduce the quality of the work. Adjustments must be made as soon as possible to to get the team back on track and refocused.

Scrums Formal Events

Scrum advises we should use four formal events for inspection and adaptation. These are all key meetings where any issues, impediments or blockers should be called out and actioned upon as soon as possible.

We will be looking into each one of these Events in much more detail throughout this series:

  • Sprint Planning
  • Daily Scrum
  • Sprint Review
  • Sprint Retrospective