article thumbnail

The 6 Stances Of A Scrum Master

Scrum.org

In 2010 I started my first assignment as a Scrum Master. Mostly intended to help myself reflect on my role, receive feedback from other Scrum practitioners, and make improvements accordingly. Over the years, the sum of these blog posts resulted in the paper “ The 8 Stances Of A Scrum Master ”.

SCRUM 226
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.

Agile 216
Insiders

Sign Up for our Newsletter

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

article thumbnail

How We Made Our Customer The Product Owner

Scrum.org

From 2010–2015 I worked as a Scrum Master for a web agency. When I started, Scrum wasn’t used at all. In the context of Scrum, the Product Owner plays an essential role. Word of warning, this isn’t going to be a “Scrum Guide post”. That’s in a nutshell the approach we used within our Scrum team.

article thumbnail

Scrum im Selbststudium – Teil 3: Warum ist die regelmäßige Überprüfung und Anpassung erfolgversprechender als Vorabanalyse und detaillierte Planung?

Scrum.org

Artikel der „Scrum im Selbststudium“-Artikelreihe. Starten wir von Anfang an: Was ist Scrum? Hinter diesen Begriffen verbergen sich die Antworten auf die Fragen: Wann sollte Scrum eingesetzt werden? Warum funktioniert Scrum? Wie funktioniert Scrum? Willkommen zum 3.

SCRUM 146
article thumbnail

Why Agile Transformations sometimes fail

Scrum.org

Based on my experience working in agile environments since 2010, I did some research and had general observations on the topic. Usually, top management is at some point aware of Agile activities in the company, Scrum adoption, although they leave it to the teams. It becomes an organizational impediment. Products are rarely defined.

Agile 253
article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition. The Scrum Framework.

SCRUM 337
article thumbnail

Risk Management Resources

Herding Cats

255, April 2010. 24, 2010. “A Problems with scoring methods and ordinal scales in risk assessment,” Douglas Hubbard and Dylan Evans, IBM Journal of Research and Development , 54(3):2, May 2010. 29 April 2010. Finucane, Ellen Peters, and Donald MacGregor, Risk Analysis , Vol.24, 920, November 2004. 5, May 2013, pp.