<< IIS7 & WCF error | Home | Ivory Tower Architect >>

Development Project Archetypes

As part of writing our book, Kyle and I have spent some time coming up with archetypes that exist on many of the software projects that we've been on.  Our goal is just to describe what we've seen so that people can better identify them in their journeys.  Of course this had to be written in a dry, sarcastic manner.  I'm going to keep updating this post with the links for the new archetypes as I post the series.

  1. Ivory Tower Architect
  2. The Absentee Client
  3. The Disenfranchised Client
  4. The Process-Heavy PM
  5. The Front of the Magazine Architect
  6. The Ex-Tech Project Manager
  7. The Disinterested Developer
  8. The Skeptic
  9. The "Experienced" Developer
  10. The Hero Developer
  11. The Over Protective DBA
  12. The Enhancing Tester/QA
  13. The ‘Oooo…Shiney!’ Developer
  14. The Possessive Developer

posted @ Wednesday, April 01, 2009 9:31 AM

Print

Comments on this entry:

# re: Development Project Archetypes

Left by Basil Vandegriend at 4/6/2009 8:01 PM
Gravatar
I'm loving these archetypes so far. Are you planning to cover any positive archetypes, or only archetypes of doom? :)

Here are some suggestions for other archetypes based on my experience:
- Ostrich PM: Buries head in sand whenever a risk or issue appears hoping it goes away.
- Harmful Developer: The more hours they spend coding, the worse off the project is.
- Rigid QA Group: Insists on formal documentation of test cases and test results with 100% functional coverage before they start their testing.

# re: Development Project Archetypes

Left by Luis Rocha at 4/6/2009 8:22 PM
Gravatar
LOL when reading these archetypes and surprised of how many of them I've seen so far.

Here goes one suggestion based on my experience:
- The Unbreakable Developer: Those developers who think that their code is unbreakable. They think that unit tests are not necessary, that continuous integration is a waste of time, and they never add comments to the code or either to the revision control changelists. The unbreakable developer results in broken software.

# re: Development Project Archetypes

Left by Marta at 4/22/2009 2:38 AM
Gravatar
A good archetype that has been blogged about intensively in the testing community is the Quality Police. See http://www.stickyminds.com/sitewide.asp?Function=edetail&ObjectType=COL&ObjectId=3543

# re: Development Project Archetypes

Left by Adam D. at 4/27/2009 6:04 PM
Gravatar
Nice series, Don. Can't wait for the book :)

# re: Development Project Archetypes

Left by web development at 10/15/2009 7:55 AM
Gravatar
Interesting,

the book is out now?

Anyway, thanks for the post
Comments have been closed on this topic.