- They provide ambiguous project specifications.
- They expect that the developer should understand the requirements based on his past experiences. If she doesn’t she is not a developer, she is just a coder!
- They shout on you when there is even a little issue identified in the system. They love to play the blame game.
- They derive project delivery dates from your casual chat or phone call with them and follow up with you before 2 hours of their assumed delivery date, and say, “I really want this ready, my client is waiting for this to be completed. I will be in a soup if I can’t deliver it today”
- They focus on finding the problems, not the solutions.
- They get confused too often and do a great job in confusing you.
- They don’t pay on time.
See Also:
- Seven Habits Of Highly Ineffective People
- Project Manager Who Loves Chatting with the Client At Her Convenient Time
- Twenty Traits Of Software Project Sponsors Who Have The Power To Screw-up An Offshore Outsourcing Engagement
- Dependable Project Manager, A Pen and Few Papers
- Distinction Between Issues And Problems And How To Deal With Them
- Twelve Traits of Dependable Project Managers
- Eight Practices To Convert Ineffective Project Sponsor Into Effective One

