Remove 2004 Remove Influencer Remove Software Development
article thumbnail

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

Scrum.org

This is the ability of team members to act in concert without explicit coordination (MacMillan, Entin & Serfaty, 2004). This effect has been observed with flight crews (Orasuna, 1990), nuclear plant control crews (Waller, Gupta & Giambatista, 2004), and work teams (Urban et. In Achieving Quality in Software (pp. Kearney, E.,

2004 251
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 230
Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

Software development is (generally speaking) very complex. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’. 2004) _How can we think the complex?Retrieved Their article inspired me to apply the same insights to Scrum and to extend it with my own. Being there.

2002 225
article thumbnail

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

Scrum.org

Barry : Failed software development projects. I was responsible for managing software development projects. Developers, because of the growing crunch-culture. I have a pretty diverse background, from scientific training to software development and from running a company to being part of a team.

Agile 143
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.

SCRUM 78
article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Now To Risk Management.

article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

An Introduction to IMP/IMS , 17 Oct 2004. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015.

2003 54