Technical management is like driving. When you do it correctly, no one pays attention, once an error is wrong, the problem will follow. The following is the Team management experience in INTERVIEW Manager in 11 years, and you must pay attention to every point.
1. Don't repeat the mistakes that others have made in the past two or thirty years
This sentence comes from Steve McConnell, IEEE software editing and software development best-selling writer. McConnell's work includes classic book "Code Complete". McConnell believes that "a large number of reading" is the best way to avoid errors.
2. 80% of management is to choose the right candidate
SCOTT Adams, Dilbert comics author believes that a good project manager must create a person using the environment. All project managers should read a new book of Tom Demarco and Tim Lister, "People: Productive Projects and Teams" (2nd Edition, Dorset House, 1999).
3. Always try to hire people than you
Don't make your own yourself becomes a bottleneck of the project. Organize a smart team, give them enough resources and rules to solve problems, let employees solve problems themselves.
4. Don't waste time
Tom Bragg, the Chief Technology Officer of IntelliSys Technology Corp. believes that too many projects cannot be in trouble as scheduled. The reason why the delay is usually caused by other tasks interference, personnel change, and un-on-time manager.
5. Optimal is not necessarily the largest
Another suggestion for Tom Bragg is: Close attention to what happened after the start of the project. Bragg said: "Plan your work and then on schedule, over-tension work intensity is often caused by the decrease in productivity, possibly maintaining the intensity of work within 50 hours per week.
6. Real, fair estimate
Project managers should avoid the trap of "modification plan according to the desire of the manager". "An effective estimate is characterized by the estimated time and money than the actual situation and the probability of high," Bragg said.
7. Make your organization structure more efficient
In many cases, you can use another organizational structure with now. Take a look at the development team of Apache Web Server, their hierarchical organization is not clear, but has developed successful products.
8. Using free tools on WWW
From http://sunnet.usc.edu/winwin/winwin.html, you can download tools developed by Barry Boehm, which can combine W theory (WINWIN model) and spiral models. At the URL of the Project Management Institute, you can download its online manual. From www.spmn.com you can see some advice from the CMM model and two sets of tools: Control Panel and Risk Radar. Control Panel is an Excel form, due to monitoring productivity and quality; Risk Radar is an Access database, quantitating the risk of the project.
9. Don't read the old programmer
Rehabilitation existing programmers have valuable value than employing new graduates. Old programmers have rich experience on multiple projects, through new skills training, their experience and knowledge will help young programmers (including project managers) to save time and money.
10. Select the correct workflow for your project
Not all projects apply to a development process. Intel has regularly checks the work quality of each development team, if delayed delivery or quality issues, Intel encourages the group to improve their workflow.
11. Do your survival plan
