Twenty Two Traits Of Procrastinating Software Developers (Who Should Not Be In Your Team)

Photo Credit: yvescosentinos Flickr photostream

Photo Credit: yvescosentino's Flickr photostream

  1. Intentionally forgets some tasks.
  2. Directly or indirectly engages in organizational politics.
  3. Works for long hours just to show that she is working for long hours – effective hours are not more than 2 or 3 per day.
  4. Always talks about the problems, disasters and how a task cannot be accomplished.
  5. Thinks what she knows about the technology is the only correct way to implement it.
  6. Lack of integrity. Doesn’t honor her words.
  7. Not trustworthy.
  8. When she thinks she won’t be able to meet the scheduled release, she’ll give you 1000 excuses vividly.
  9. Flatters her boss – believes that this way she can be respected among others.
  10. Takes initiatives but never accomplishes the task.
  11. Reactive. Thinks win-lose.
  12. Does not have good listening capabilities. Operates from her past beliefs only rather than the facts.
  13. When client has asked her to do a specific task, she works on something else! And then rationalizes why she worked on something else.
  14. Never begins with the end in mind. When an adverse situation comes, throws its responsibility on someone else.
  15. Does not have good soft skills and does not believe she needs any.
  16. Has zero business sense. Cannot think from the business perspectives.
  17. Rude with colleagues. Often comes with the problem with fellow colleagues.
  18. Does not have good family life.
  19. When she works overnight, people think that she is committed – in fact it is because of something she overlooked in the early stages of the project.
  20. When she is working as a full time dedicated developer for an offshore company, takes personal work from her boss and invest half of the day working on that.
  21. Has a GREAT power to demotivate the team she is working with.
  22. Loves photography (just kidding!) Thinks Negative.

Mentor, coach, guide or fire (if nothing works) such software developers but DO NOT allow them to be in  your team.

See Also:

  1. Twenty Traits Of Software Project Sponsors Who Have The Power To Screw-up An Offshore Outsourcing Engagement
  2. Zen of Team Handling for Software Projects
  3. Twelve Traits of Dependable Project Managers
  4. How Do You Know Your Team Is Motivated 30
  5. Leadership Virtues That A Software Project Manager Should Have
  6. How To Inaugurate Effectiveness In Your Project Team
  7. How Team Relationships Are Affecting Your Ongoing Projects?

8 Responses

  1. Twitter Comment


    Thx! RT @tnvora: 22 Traits Of … Software Developers (Who Should Not Be In Your Team) by @utpalvaishnav – [link to post]

    Posted using Chat Catcher

  2. Twitter Comment


    UV.Blog:22 Traits Of Procrastinating Software Developers (Who Should Not Be In Your Team) [link to post] #pmot

    Posted using Chat Catcher

  3. Twitter Comment


    Twenty Two Traits Of Procrastinating Software Developers (Who Should Not Be In Your Team) by @utpalvaishnav – [link to post]

    Posted using Chat Catcher

  4. Twitter Comment


    RT @utpalvaishnav 22 Traits Of Procrastinating Software Developers (Who Should Not Be In Your Team) [link to post] #pmot #pm

    Posted using Chat Catcher

  5. Twitter Comment


    Thx! RT @pmtweetx: RT @utpalvaishnav 22 Traits Of…Software Developers (Who Should Not Be In Your Team) [link to post] #pm

    Posted using Chat Catcher

  6. Simply Awesome :)

    But please advise how to take care from Such kind for Team Members :)

  7. Twitter Comment


    RT @utpalvaishnav Twenty Two Traits Of Procrastinating Software Developers (Who Should Not Be In Your Team) [link to post]

    Posted using Chat Catcher

  8. Twitter Comment


    Thx! RT @shahmaulikn: RT @utpalvaishnav 22 Traits Of…Software Developers (Who Should Not Be In Your Team) [link to post]

    Posted using Chat Catcher

Leave a Reply

.

CommentLuv Enabled