2 tried and true ways to frustrate and discourage your developers
Personal, Software Design Add commentsI have been reading a lot about what makes a developer want to stay or leave their current jobs or clients on some development blogs as of late.
There are two things that stuck out to me, probably because they hit home with me, that can really frustrate and discourage a developer.
1. Poor or incomplete specifications. There is nothing worse for a developer to implement code based on wrong or poor specifications. The results are never what the manager or client wanted. This results in tention on both ends and the developer ends up recoding the task. Everyone loses in this case.
It is very important for the client or project manager to lay out very precise and detailed instructions for the developer before any coding begins. This is even more important if the developer has limited or no access to the client or manager to resolve questions. The poorer the specifications the more questions and guess work the developer must do to complete the project.
Being a the lead developer in my organization I have felt the pain of redoing work and have a strong appreciation for proper planning and documentation.
2. Unreasonable expectations. This can come in many forms, from unreasonable deadlines to being expected to overcome limitations in technology. What ever the expectation both parties end up discouraged and disappointed when things fall apart.
It is essential that the client be made aware from day one what is possible in the realm of technology and timeline. It is also crucial that the person or team that communicates with the clients and relays information to the development team be very knowledgeable in these areas as well. Sales reps love to say whatever will make the sale but this can lead to some messy situations if promises cannot be delivered as stated.
Avoiding disaster
If managers can keep these points in mind, and take them to heart, when organizing projects they will be amazed at the amount of positive outcomes that will result from just a little diligence to make sure both sides stay happy and productive.
Did You Enjoy This Post?
Be sure to grab my RSS feed so you don't miss out on more great articles.
This Post Was Brought To You By
How do I save time? I use FreshBooks for invoicing.
Get Information Technology magazine subscriptions and white papers for FREE!
Did you like this post? Be sure to 2 tried and true ways to frustrate and discourage your developers
June 27th, 2008 at 3:50 am
I would add another one: Do not recognize efforts (and reward it with money, promotion, …).
June 27th, 2008 at 6:19 am
That is definately a valid point. there is nothing worse that feeling like your career is going nowhere.
June 29th, 2008 at 6:12 pm
Poor or incomplete specifications is a very blurry subject. I’ve found that my developers like to be given a goal with the freedom to develop a solution. Great developers come up with multiple solutions, bad ones complain that no one told them ‘how’ to solve the problem.
No one knows the capabilities of an application like the developer does. I appreciate the developer who helps me to fill out the precision involved to complete the solution.
June 29th, 2008 at 7:39 pm
I am not talking about being told every detail but being told the goal is to create an app to manage real estate contracts without being told how the industry works is just asking for trouble.
July 3rd, 2008 at 7:34 pm
Good point! I’d also add to the list:
– Lack of challenge
– Micromanagement (that includes enforcing strict work schedule)
– and of course, inadequate pay