Remove 2019 Remove Development Team Review Remove Exercises Remove Risk
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 232
article thumbnail

Stories about Stories in Agile Development

MPUG

Things such as value delivered, cost incurred, risk involved, knowledge gained etc. There will be work items to improve the infrastructure, improve processes, find a response to a risk, etc. Every development team uses a number of infrastructure related to coding, debugging, deployment, and configuration, among many others.

Agile 99
Insiders

Sign Up for our Newsletter

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

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. Benefits Good strategy aligns team members and helps everyone connect to the same ‘why’. Keep them risk-free.

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 216
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 227