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

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

Scrum.org

Join more than 100 peers from May 27-29, 2021 , for the Virtual Agile Camp Berlin 2021, a non-profit live virtual Barcamp using open space technology principles and practices. The team addressing unplanned priority bugs. Has the level of technical debt increased or decreased during the last Sprint?

SCRUM 222
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. Increased software quality can be demonstrated by measurably less technical debt, fewer bugs, and less time spent on maintenance.

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

If the developer or customer is unsure about a solution to a technical problem or estimation for a story, spike can be developed to answer these questions. Every development team uses a number of infrastructure related to coding, debugging, deployment, and configuration, among many others. Exercise on 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 197
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. Keeping technical debt at bay. A good Scrum Team pays attention to the preservation of an application’s technical health to ensure the Scrum Team is ready to actually pursue an opportunity in the market.

SCRUM 224
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 210
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.