2004 Influencer Software Training 
Scrum.org
AUGUST 1, 2022
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.,
Scrum.org
MAY 26, 2020
“ Christiaan : A friend of mine started a software company. It resonated strongly with my beliefs about personal autonomy and all my prior training as a psychologist.”. Barry : Failed software development projects. It resonated strongly with my beliefs about personal autonomy and all my prior training as a psychologist.”.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MARCH 17, 2019
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.
Gunther Verheyen
FEBRUARY 27, 2024
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.
Rebel’s Guide to PM
MARCH 16, 2022
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.
Scrum.org
FEBRUARY 3, 2020
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’.
Rebel’s Guide to PM
FEBRUARY 14, 2018
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.
Expert insights. Personalized for you.
230 
Let's personalize your content