What is inspected in the sprint retrospective?

What is inspected in the sprint retrospective?

Learn About the Sprint Retrospective Event The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. They may even be added to the Sprint Backlog for the next Sprint.

What does inspection mean in Scrum?

empirical process control
Inspection is a critical aspect of empirical process control as it what makes the Scrum framework adaptive to complex problems. One example is when the Scrum team shows the progress of the product outcome to the customer (client) at the end of each sprint to get their feedback. …

Who does inspection in Scrum?

Inspection: Inspection in this context is not an inspection by an inspector or an auditor but an inspection by every- one on the Scrum Team. The inspection can be done for the product, processes, people aspects, practices, and continuous improvements.

What is the purpose of the sprint Retrospective inspect how the last sprint went with regards to people relationships process and tools?

The purpose of the Sprint Retrospective is to: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work.

What’s the purpose of a sprint retrospective in scrum?

As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.

Do you need to be present for a scrum retrospective?

The Team and Scrum Master need to be present. The Product Owner is welcome but not required to attend. Sometimes the Scrum Master can act as an effective facilitator for the Retrospective, but it may be better to find a neutral outsider to facilitate the meeting.

Who should and should not be included in a sprint retrospective?

Scrum Master – The Scrum Master is the facilitator of the team, the person is responsible for promoting and supporting by helping everyone understand Scrum theory, practices, rules, and values. Product Owner – The product owner is the leader responsible for maximizing the value of the products created by a scrum development team.

Why are product owners not included in retrospective meetings?

Some think that his or her presence is vital but on the other hand, some feel that the product owner’s presence defeats the main purpose of retrospective meetings which is to provide a safe and open place for feedback discussions because it might inhibit the team from being completely honest or revealing difficult issues.