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

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

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

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

Scrum.org

Software development is (generally speaking) very complex. Why our brain is not built for software engineering. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’. 2004) _How can we think the complex?Retrieved This limits our ability to deal with complex problems.

2002 225
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 143
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.