Remove 2004 Remove Software Remove Software Development Remove Training
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 236
article thumbnail

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

Scrum.org

“ Christiaan : A friend of mine started a software company. He sold solutions, I developed them. It resonated strongly with my beliefs about personal autonomy and all my prior training as a psychologist.”. Barry : Failed software development projects. Barry : Failed software development projects.

Agile 101
Insiders

Sign Up for our Newsletter

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

article thumbnail

Managing Virtual Teams Successfully

The IIL Blog

Online gaming collaboration can be traced back to the introduction of the personal computer and software developers and came to life in the early 1990s when the Internet was introduced. Resources: Number of participants, software, and systems required, facilities, etc. Quality: Complexity – how challenging.

article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. An Introduction to IMP/IMS , 17 Oct 2004. Capabilities Based Planning.

2003 54
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 71
article thumbnail

What is Taylorism, and why Waterfall is just the tip of the iceberg!

Scrum.org

The modern school system was developed during the industrial revolution to train factory workers. The result is that many people have been trained from an early age to be factory workers. And so we created departments so we could centralise training and knowledge on a single topic. Put people into ability-based groups.

2001 219
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. Most of us find it very hard to concentrate on the train-of-thought necessary for continuous thought. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’.

2002 209