Remove 2019 Remove Development Team Review Remove Exercises Remove Process
article thumbnail

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

Scrum.org

This attitude is precisely why the 47 Scrum Master Interview Guide exists: Prevent imposters from slipping through the hiring process and causing damage. The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. Question 44: First Steps of a New Scrum Team.

SCRUM 224
article thumbnail

Scrum Master Interview Questions (1): Scrum Master Role

Scrum.org

As somebody hiring for a Scrum Team, you need to determine for yourself what works for your organization — which is a process, not a destination. Being a Scrum Master does not entail, and should never entail, enforcing processes. Generally, insisting that the team achieve specific KPI (e.g.

SCRUM 231
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

Now, imagine a software development project. The process is a complex one with many stakeholders involved over months, sometimes years. In this process, written requirements with written words are many times inadequate, sometimes even inaccurate, and most of the time said requirements don’t convey the real intent.

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 200
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 212
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. This first set of the Scrum Master theses addresses their role in the Scrum process: Scrum is not a methodology, but a framework. Being a Scrum Master does not entail, and should never entail, enforcing processes.

SCRUM 225
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.