Patterns of Failure: Acquisition Archetypes
• Collection
Publisher
Software Engineering Institute
Topic or Tag
Abstract
The SEI is developing Acquisition Archetypes to help the software community identify, manage and prevent recurring patterns of counter-productive practices in software acquisition. This work is based on experiences with actual programs, and uses concepts from systems thinking to characterize and analyze dynamics. A set of briefs is being developed as an initial part of this effort to describe some of the most common patterns, and assist acquisition programs in handling and avoiding them.
Collection Items
Acquisition Archetypes: Firefighting
• White Paper
By Software Engineering Institute
All hands on deck helps put out the immediate blazes threatening projects, but falling into a routine of constant firefighting is not the way to guide a project across the …
Read
Acquisition Archetypes: The Bow Wave Effect
• White Paper
By Software Engineering Institute
From the Acquisition Support Program, one in a series of short papers on acquisition patterns of failure.
Read
Acquisition Archetypes: Feeding the Sacred Cow
• White Paper
By Software Engineering Institute
Some programs take on a life of their own—privileged, and woven into an organization's existence. But when "sacred cow" projects begin to go wrong, that privilege and protection makes fixing …
Read
Acquisition Archetypes: PMO versus Contractor Hostility
• White Paper
By Software Engineering Institute
Everyone intends the best in project-driven marriages of PMOs and contractors, but good intentions can't overcome the hostility generated by loss of trust and squabbles in poorly developed relationships.
Read
Acquisition Archetypes: Staff Burnout and Turnover
• White Paper
By Software Engineering Institute
Applying more pressure on staff can temporarily increase productivity, but burnout soon sets in.
Read
Acquisition Archetypes: Everything for Everybody
• White Paper
By Software Engineering Institute
When projects attempt to please too many customers, complexity mounts, schedules slip, costs expand, and no one is happy.
Read
Acquisition Archetypes: Underbidding the Contract
• White Paper
By Software Engineering Institute
From the Acquisition Support Program, one in a series of short papers on acquisition patterns of failure.
Read
Acquisition Archetypes: Longer Begets Bigger
• White Paper
By Software Engineering Institute
Planning for a long development period doesn't always solve acquisition scheduling problems. Sometimes it makes them worse.
Read
Acquisition Archetypes: Robbing Peter to Pay Paul
• White Paper
By Software Engineering Institute
This April 2009 whitepaper is one in a short series of acquisition failures. This paper focuses on the problems of underspending, which can result in funds being shifted from one …
Read
Acquisition Archetypes: Brooks' Law
• White Paper
By Linda Levine, William E. Novak
This April 2009 whitepaper focuses on the problems of underspending, which can result in funds being shifted from one acquisition program to another.
Read
Acquisition Archetypes: Happy Path Testing
• White Paper
By Linda Levine, William E. Novak
When time and budget are tight, it's tempting to follow the "happy path" in testing. But be careful: it may be a path that brings your program great unhappiness.
Read
Acquisition Archetype: Shooting the Messenger
• White Paper
By Linda Levine, William E. Novak
When problems are detected in programs, everyone needs to listen and work together towards a solution. Shooting the messenger only delays the process, and hurts program morale.
Read