2004 Influencer Software Software Developers 
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.,
Herding Cats
OCTOBER 30, 2018
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
MAY 26, 2020
“ Christiaan : A friend of mine started a software company. He sold solutions, I developed them. Barry : Failed software development projects. Barry : Failed software development projects. I was responsible for managing software development projects. During Christmas of 2004!
Herding Cats
MAY 10, 2019
This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 920, November 2004. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.
Herding Cats
MAY 11, 2019
This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.
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.
Scrum.org
AUGUST 17, 2020
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.
Expert insights. Personalized for you.
232 
Let's personalize your content