article thumbnail

Scrum Master Interview Questions (4): From Metrics to Kicking off Scrum to Scrum Anti-Patterns

Scrum.org

The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range. Question 44: First Steps of a New Scrum Team.

SCRUM 223
article thumbnail

Scrum Master Interview Questions (1): Scrum Master Role

Scrum.org

A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. solely through the Product Owner) because this hurts transparency and negatively affects the team’s performance. There is greater respect among stakeholders for the product delivery teams. Question 03: Impediment Remover.

SCRUM 229
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Stories about Stories in Agile Development

MPUG

For example, you have analysis stories to analyze on a risk, have process improvement, or to analyze on an impediment, which is proving to be time-consuming, such as: Review the suggestions made by our partners to find out if we can implement some of those suggestions. Exercise on Stories. Infrastructure Stories.

Agile 99
article thumbnail

Scrum Master Interview Questions: Scrum Anti-Patterns

Scrum.org

Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment. Question 45: Scrum Master Anti-Patterns.

SCRUM 198
article thumbnail

32 Scrum Stakeholder Anti-Patterns

Scrum.org

InfoQ’s recent ‘ Culture & Methods – the State of Practice in 2019 ’ edition found that new converts to Scrum, for example, will recruit themselves mostly from the late majority and laggards. Copyright notice : InfoQ, 2019. Any of the examples will impede the team’s productivity and might endanger the Sprint goal.

SCRUM 213
article thumbnail

70 Scrum Master Theses

Scrum.org

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak Development Team meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.

SCRUM 223
article thumbnail

Strategy vs. tactics: How to use both to build better products

Planio

6 rules to follow How to bring strategy and tactics together: 5 examples for different teams 1. Product development teams 2. Digital marketing teams 3. Sales teams 4. Customer service teams 5. A successful strategy isn’t a set-and-forget exercise. A successful strategy isn’t a set-and-forget exercise.