In the PSMI guide, you already know that scrum is founded on Empiricism and that Transparency promotes visibility; next, you can Inspect the product or the work done and, if needed, Adapt. But how can you put this down on scrum? How do the five repeating events, three artifacts, and three roles work empirically?


The Scrum artifacts permit the work’s visibility, which helps Transparency; remember that only with it can you have an inspection. The scum artifacts are the object of the inspection. You can look at:

  • The Product Backlog makes transparent all the work needed for the product. You can even put high-level ideas like a reminder di things to do in the product backlog. The Scrum Team acquires more detail during each sprint and refines the product backlog. This way contains all the knowledge; it’s the “only source of truth.
  • The Sprint Backlog collects items selected from the Product Backlog needed to achieve the sprint goal. This makes transparent what the product team is working on.
  • The Increment is the collection of all the items completed by the team during the sprint. This provides transparency on the work done during the sprint.

To inspect the artifacts we obviously need a commitment; that is a baseline to check with. Remember that:

  • The Product Backlog’s commitment is the Product Goal. With the product goals, you can inspect its success and state.
  • The Sprint Backlog’s commitment is the Sprint Goals. Only with the sprint goals can you construct a good sprint backlog, select the correct item and then inspect the state of the work. It also gives visibility about what we are working on in the current sprint.
  • The Increment’s commitment is the Definition of Done. With a list of requirements to meet, it is easy to inspect an increment of an item and say if it is an increment.

The Scrum event is the action of Inspection and Adaptation. In this event, you look at the work done and make decisions to improve the work in the next sprint. You can look at:

  • The Sprint is the container of all the other four events. It’s a way to decompose a complex problem into a minor problem that you can work on. Each event in a sprint provides a specific opportunity for inspection and adaptation;The
  • The Sprint Planning is where the scrum team defines the sprint goal, selects the item to work on, and makes an actionable plan. The selection of items came from the inspection of the Product Backlog. The Sprint Backlog and the Sprint Goals permit adaptation during the current Sprint;
  • The Daily Scrum is where the Developers inspect the state of the work done, and on this inspection, they adapt their future results;
  • The Sprint Review is where all the Scrum Teams and stakeholders work together to inspect the increment. In this event, they can also find new ideas adapting the future work;
  • The Sprint Retrospective is all about inspecting and adapting the way of working.

In order to facilitate collaboration and reduce complexity the Scrum framework provide only three role. You can look ath:

  • The Product Owner knows what is valuable for the product, and it’s the only person (not a committee) who has the last words on it. This role permits an agile adaptation.
  • The Developers are those who do the work for the increment. Therefore, they need to have the necessary skills to do the job and are self-managed, without a boss. This is all about the team’s independence from external constriction (external from the group, maybe internal of the company) because the framework doesn’t work without it. What if, for the current sprint, you need a Graphic Designer for an item and your company didn’t have one available at the moment? You get stuck or lose in agility.
    The Scrum Master is the people who know how the empirical process works and help the Scrum Team and the Organization work on it.

For the exam you need to remember that:

  • The scrum artifacts foster Transparency because they are the object of the inspection;
  • For the inspection of artifacts, we need the correct commitments;
  • The scrum events is all about making the inspection and the adaptation;
  • The sprint planning inspect the product backlog and permit adaptation through the sprint goal;
  • The sprint review permit inspection on the increment and adaptation;
  • The sprint retrospective permit inspection on the way of work;
  • The Product Owner permits fast adaptation;
  • The Scrum Master is who best know scrum and foster the empirical process;
  • The Developers are self-organized and have all the skills needed because without it all the Scrum framework doesn’t work.

References:

Share on: