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. For this purpose it defines three roles, a scrum master, a product owner and a development team, made up of several team members.

SCRUM 397
article thumbnail

Project Gates: The Janus-like Guardians of Product Development

MPUG

One might conclude that agile approaches to project management, such as Scrum, mean there is no need for gate reviews. We say the same thing if one adopts gate reviews for every product development project. Let’s explore a typical product development project’s phases, goals, and metrics reviewed at each gate.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Why Great (Scrum) Teams Have A Mind Of Their Own

Scrum.org

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. From Individual Models To Team Mental Models. References.

2010 231
article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

Team cognition is similar in the sense that the entire team can be thought of as a body, where each member (the limbs) has to learn how to coordinate their work effectively to move forward. This shared understanding is captured in the “team mental models” that drive team cognition. It takes time to develop teams.

article thumbnail

Creating a Risk-Adjusted Backlog

Leading Answers

Assessing the chances of loss or gain occur throughout all forms of business and relies on taking an economic view of decision making. I wrote about these ideas when I started blogging in 2006 as  Risk Profile Graphs. I do not think the teams have been weak at threat avoidance. Risks Actions in the Backlog.

Risk 145
article thumbnail

Why Agile Engineering Practices in Software Development Are Essential to Achieve Agility

Scrum.org

For sustainability, robustness, quality, customer service, fitness for purpose and true agility in software development teams, it is important for there to be continuous investment in agile engineering practices. [1] Sheppard & W.

article thumbnail

The “ScrumAnd” Stance (requiring thought and discipline)

Gunther Verheyen

Since Scrum’s inception in 1995 and the definition of ‘Agile’ as a set of values and principles in 2001, Scrum gradually became the most preferred way for people, teams and organizations worldwide to become more Agile. Agile crossed the chasm (2005-2006) and by now the 3rd Scrum Wave has risen. And then complexity comes into play.

2005 73