Remove 2004 Remove Agile Remove Influencer Remove Software
article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. This is the ability of team members to act in concert without explicit coordination (MacMillan, Entin & Serfaty, 2004). Many studies have found that psychological safety has a positive influence on team effectiveness (Edmondson, 2014).

2004 225
article thumbnail

The Origins of Scrum Might Not Be What You Think They Are (Wisdom from Rafael Sabbagh)

Gunther Verheyen

As the earlier excerpt shows, it was this book that introduced the idea of applying the practices described by Takeuchi and Nonaka to software development. The authors explain why the waterfall model doesn’t work for software development, and they offer possible alternatives, among them (what they call) Scrum. 20, 2004: pp.

SCRUM 71
Insiders

Sign Up for our Newsletter

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

article thumbnail

Agile Movers & Shakers (6): The Liberators Christiaan Verwijs & Barry Overeem

Scrum.org

TL; DR: The Agile Movers & Shakers Interview w/ Christiaan Verwijs & Barry Overeem. If so, you can subscribe here and join 26k agile peers. The Agile Movers & Shakers Interview with The Liberators Christiaan Verwijs & Barry Overeem. What brought you to ‘agile?’. Christiaan : A friend of mine started a software company.

Agile 97
article thumbnail

Test First approach sounds simply enough, right?

Scrum.org

If you’re not already aware, the way you think of testing within an agile approach is fundamentally different to the traditional one. But Kent, and others, found that writing test first had a tremendous positive effect on the software architecture and design of software too: Testable. Behaviour-Driven Development (est 2004).

article thumbnail

Summary of Capabilities Based Planning

Herding Cats

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109
article thumbnail

Agile Unplugged: EP01 | Mike Cottmeyer and Brian Sondergaard

Leading Agile

Agile Unplugged is your chance to explore LeadingAgile’s freshest ideas, mental models, frameworks, and solutions with the people that are actually doing the work of leading large-scale Agile Transformation, out in the field. What was that, probably 2004, or ’05 or something in that kind of range, I think?

Agile 103
article thumbnail

In-Depth: How Easily Biases Distort What We Believe (In The Workplace)

Scrum.org

It happens, for example, when we don’t trust a certain person or group of people, and then only see behavior that fits with our belief (or even interpret it as such) without considering observations where they don’t (Oswald & Grosjean, 2004). The influence of initial anchoring is less, especially when I take care not to anchor myself again.

2015 212