Improving processes and content

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

Improving processes and content

Important part of the scrum retrospective , however, is the reflection on previous experiences. Which participants participate in the  defin. As a rule, the developers and the scrum master are present. However, the product owners, for example, often also take part in the meetings. If it is a team retrospective , only the representatives of the team are present. In this case, the scrum master and the product owner do not participate. In a so-call overall retrospective, on the other hand, a representative of the team the scrum master.

Scrum retrospective is not generally

The product owner and the managers of the lines are present. Rules the scrum retrospective does not work without fix rules . However, no comprehensive Brazil Phone Number List catalog of rules is requir here. Instead, two rules are of great importance: the golden rule :  is that all participants should treat each other with appreciation and respect. The teamwork is in the foreground, so that all participants should contribute to the meeting with their best knowlge and skills. Harsh criticism or blame is not desir. The vegas rule bas on the famous saying.

Brazil Phone Number List

The golden rule of the scrum retrospective

What happens in vegas  stays in vegas, the rule also applies to the scrum retrospective: what is said here stays exclusively with the participants of the Marketing List meeting. After all, the whole approach of the scrum retrospective is bas on the principle of trust. Goals different goals are pursu with the scrum retrospective . Basically, the meetings are suitable for . Possible Bottlenecks can be identifi and their effects on further work can be discuss. Another goal is to continuously improve communication between the scrum master, the developers and the product owner. In addition, every meeting offers space for feback in the team and provides space to eliminate misunderstandings. Phases the scrum retrospective can generally.

Leave a comment

Your email address will not be published. Required fields are marked *