Remove 2004 Remove Influencer Remove Software
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 247
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 229
Insiders

Sign Up for our Newsletter

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

article thumbnail

Test First approach sounds simply enough, right?

Scrum.org

A year later, in 2000, Kent Beck published another book called “ Test Driven Development by Example ” and explains Test Driven Development (TDD) is a software process and not about writing tests before the code with one more important aspect – refactoring. Behaviour-Driven Development (est 2004). Add a test. Independently Deployable.

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 78
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

How to Create a Project Team Culture with Colin Ellis

Rebel’s Guide to PM

One of the things I noticed probably post 2004, when we all went a bit method crazy, was that it’s a bit of a dying art, this creating teams thing. For the last three years I was working in New Zealand, I worked as a contractor, and I had way more influence as a contractor than I ever did as a permanent employee.

article thumbnail

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

Scrum.org

“ Christiaan : A friend of mine started a software company. Barry : Failed software development projects. Barry : Failed software development projects. I was responsible for managing software development projects. Christiaan : I’ve always been developing software to help people (users, customers, myself) solve problems.

Agile 108