Thursday, July 06, 2006

How to identify you're becoming the fall guy for a project

  1. The Development team call you in for an extra day on the day they are demoing the system
  2. Asking the development team 2 hours before the demo if they need a hand getting it ready they respond, "Haven't really looked into it yet"
  3. Asking the development team 1 hour before the demo if they have a outline of what is being demoed they respond, "Haven't really looked into it, we're not going to be able to do the demo, you'll have to do it"
  4. Running through the required functionality for the demo and discovering that half of the "Completed" tasks aren't done.
  5. Developers tell you they hope for a failed system demo so the project manager looks bad.
  6. Madly developing the system to meet requirements for the demo.
  7. Attendees for the demo are 5 times the number you were informed.
  8. Attendees for the demo are all stake holders.
  9. Attendees for the demo are less than receptive to the system.
  10. Most of the Attendees expect to see functionality that is not a requirement in any phase let alone phase 1
  11. Discovering the Requirements gathered by the client haven't covered the requirements for the stakeholders.
  12. All the developers huddle over one side of the room for safety in numbers.

I have a sinking feeling about the rest of this project.... And I thought being a technical consultant would reduce my responsibility.


1 comment:

Anonymous said...

is this for real man?
that's no fun at all.

lb

(secretgeek.net... you know the one ;->)