Got this from a blog...
Project Manager thinks nine women can deliver a baby in One month.
Software Developer thinks it will take 18 months to deliver a baby.
Business Analyst thinks a baby is no good because the client really wants a tank.
Architect is the one who makes ill tempered babies lasers mounted on their heads.
Onsite Coordinator thinks a single woman can deliver nine babies in one month.
Client is the one who isn't quite sure why he wants a baby in the first place.
Marketing Manager is a person who thinks he can deliver a baby even if no man and woman are available.
CFO who wants to outsource the whole baby making thing
Resource Optimization Team thinks they don't need a man or woman; they'll produce a baby with zero resources.
Documentation Team thinks they don't care whether the child is delivered, they'll just document 9 months.
Quality Auditor is the bitchy person who is never happy with the PROCESS to make a baby.
Consultants
- Makes babies with multiple clients (at the same time).
- Practices multiple "baby-making" techniques (agile baby making is usually preferred).
- When accused of being the father, always claims "that is obviously someone else's child".
- When asked about "UNIT" testing, he always responds with "I do daily tests of my unit at every client site".
- Loses interest in any baby making activities 30 seconds after conception.
- Always leaves "the client" before the baby is complete and delivered.
Extreme Programmer always wants to make baby using paired effort
VB programmer bangs out babies super fast. Rapid ankle-biter developement (RAD).
C# programmer doesn't care so much about the baby, as the inheritance chain.
C++ programmer makes baby using Carbon, Hydrogen and Oxygen as the starting chemicals
DBA makes sure his baby is replicated, just in case the original baby dies
Super developer can make a baby in 9 days