I have had students ask me about how to get hired or who is hiring. I have also had employers ask me how to find developers when they have had a tough time hiring quality employees. These are tough questions to answer, but I have been on both sides of the table.
Category: Bosses
Project Manager – Team Lead – Manager of Development
I have been asked a few times for resources and tips for a new Project Manager, Team Lead, Manager of Development type position.
My tips are a generalization as I can pull out more resources for certain situations.
Tips
1. Have an open door
2. Don’t tell your team everything that you know. Be selective
3. Be positive in all your dealings
4. Lead by example. Do not ask your team to do anything you would not.
5. Speak clearly
6. If a developer says it will take a week, say two. If a developer says a month, say 6 weeks. Always buffer time.
7. Be real with expectations
8. Be kind, not too strict, but strict enough
9. Careful planning of project details
10. Listen to those above you and below you. You will learn stuff from everyone.
11. You are not the end all be all.
12. Fight for those who deserve it, help those who need it
13. Stay Organized
14. Meet with your team weekly with an agenda, so everyone can be prepared
15. Know what your superiors want from you
16. Know your place
17. Make sure you keep developing
18. Code reviews are a must, even yours ( can be fun for the team )
19. Earn your trust, trust your team
20. Know each team member’s strengths and use them. You cannot be everything to everyone
21. Failure is always an option – learn from each failure and success
22. Reflect on everyone project as there is always something to learn
23. Find a mentor or mentors – they can be good sounding boards
Online Resources
http://www.fenman.co.uk/activities/training-manual/team-leaders-development.html
http://andrewtokeley.net/archive/2008/05/02/how-to-become-a-development-team-leader.aspx
http://www.atlassian.com/agile/people/teamlead.jsp
http://en.wikipedia.org/wiki/Lead_programmer
Books to Read
Project Management in a Week By Mark Brown
Survival is Not Enough By Seth Godin
Made in Canada Leadership By Amal; Morissette, Francoise Henein
My Blogs
http://unlatched.com/blog_What_is_Leadership.aspx
http://unlatched.com/blog_Effective_Listening.aspx
http://unlatched.com/blog_How_a_Senior_can_Help_a_Junior_Developer.aspx
http://unlatched.com/blog_Can_Senior_Developers_Learn_From_Junior_Developers.aspx
Remember: Have fun or you will not like it. Take time off – you need breaks.
How to deal with a non-technical boss
We have all had bosses at one time or another that we had to deal with who was not technical in nature. Often we find it frustrating because we do not speak the same language and we do not know how to deal with each other. We as the employee can take the first step in understanding each other.
How to Speak?
You need to transform your speech into a language that your boss will understand. Knowing full well that your boss will not understand tech terms, programmer’s language or computer-speak; an alternate language is required. It is a bit of an art to transform your speech into something else. My father-in-law does it very well, but I am still learning. I like the idea, if my wife has trouble understanding it; it may be too techie. It is best to learn business terms that mean the same as tech terms. You also need to shed the technology details and implement business details. Chances are the non-technical boss will not care how it is done, but they will care about timelines, money and training.
How to Process?
Your non-technical manager will throw out business terms. They will tell you what they want using their business language. They may try to throw out some tech terms, but often they will use them incorrectly. The best approach is to make notes, and ask questions. Forget how you will go about accomplishing the task, but instead find out the details of the requirements.
Example: If they say they need a calculator to calculate how much to ship a box, ask questions like:
1. How is it done now?
2. Ask about rounding rules?
3. Ask if they do it by weight or size or both?
4. Ask if there is a matrix of postal codes?
5. Where do they get their rates?
Remember; they really do not care how you will program it. They just want it usable and for it to function correctly. Take your notes and ask your questions. Take everything back to your office and transform the details into a project and programming plan. Write out the formulas, draw out your user interface and write out your timelines for approval.
How to Act?
Do not get frustrated. Remember they are just as confused by you at you are of them. It is not their speciality to be technology. Treat them as a customer; it will help you respect them. Make lots of notes and repeat back to them what you hear. Use non-offensive language and body gestures. Sometimes drawing pictures will help both parties to understand.