Secret of successful project management
□ Excerpted from SDMagazine Karl Wiegers
In the best case, it is also difficult to manage software projects. Unfortunately, many new project managers are essentially not subject to any in-job training. Here is 20 successful management experience for project managers.
1 Define the standard of successful project
At the beginning of the project, to ensure that the risk bearer has a uniform understanding of how they judge whether the project has successfully successfully. Often, satisfying a predefined schedule is the only obvious success factor, but there are certain factors, such as increasing market share, gaining designated sales or sales, obtain a specific user satisfaction, eliminating a high The legacy system of maintenance needs, obtain a specific transactional amount and guarantee the correctness.
2 Identify the drive, constraints and freedom of the project
Each project requires balancing its functionality, personnel, budget, progress, and quality. We use every aspect of the above five projects or defined as a constraint, you must operate in this constraint, or define the driver corresponding to the success of the project, or define the freedom of success, you can Adjust within a specified range. For details, please refer to our "Creating a Software Engineering Culture" (Dorset House, 1996).
3 Define product release standards
In the early stage of the project, we must decide what criteria to determine if the product is ready to be released. You can put the release standard based on how many high priority defects, performance metrics, fully operable, or other aspects indicate that the project has reached its purpose. No matter what standard you have chosen, it should be realized, measurable, documentated, and "quality" with your customers.
4 communication commitment
Despite the commitment of impossible, never make a commitment you can't guarantee. What can communicate with customers and managers can have a good reputation when they actually get it. Your previous project's data will help you make persistent
According to this, although this does not have any truly defense effect for people who don't make sense.
5 written a plan
Some people think that it is not as good as spending time to write code, but I don't think so. The difficulty part is not a write plan, and the difficult part is this plan - thinking, communicating, weighing, communicating, summing up. You need to analyze the problem that the problem needs to be taken, and it will reduce the accident after the project will bring you.
6 decompose the task into an inch size small round stone
Small round stone in inches is a narrowed milestone. Decompose big tasks into multiple small tasks to help you estimate them more accurately, exposure to work activities you may not think in other cases, and ensure more accurate, fine status tracking.
7 is a general task development plan worksheet
If your group often assumes a specific general task, if you implement a new object class, you need to develop an activity checklist and plan worksheet for these tasks. Each checklist should include all steps that this big task may need. These checklists and worksheets will help the team to determine and evaluate each instance of each instance of the big task he / she must handle.
8 Plan. Posts the best and change work after the quality and control activities
Almost all quality control activities. Such as testing and technical reviews. It will find defects or other possible possibilities. Your project progress or work segmentation structure should be modified after each quality control activity, as a separate task involves it. If you don't have to be used as any changes, it is very good, you have already taken the plan in front of this task. But don't look at it.
9 For the process improvement schedule
Your team members have been flooded in their current project, but if you want to upgrade your group to a higher software engineering ability, you must invest some time in process improvement. Leave some time from your project schedule, because software project activities should include process improvements that can help you have a more successful day. Don't put 100% of your project members into project tasks, and then surprised why they don't have any progress in active improvement. 10 Risk of management projects
If you don't identify and control risks. Then they will control you. Take some time collective discussion possible risk factors while the project plan, assess their potential harm, and determine how you mitigate or prevent them. To a brief guide to a software risk management, see my article "Know your Enemy: Software Risk Management" (OCT.1998).
11 According to the work plan, not the calendar
People usually estimate with calendar time, but I tend to estimate the number of work plans (in people-time units) associated with tasks, and then convert the work plan to the calendar time estimate. This conversion is based on how much effective hours spending on project tasks, and any interrupts or burst adjustment requests, meetings, and all others will disappear.
12 Don't arrange more than 80% of them
Tracking your group members actually cost average the average number of hours of project designation; it will be surprised. The overhead of the task switches related to our many activities we have to do, significantly reduced our work efficiency. Don't just because someone spends 10 hours a week, it will assume that he or she can do 4 this task immediately. If he or she can handle 3 tasks, you are fortunate.
13. Place the training time in the plan
Determine how much time your team spent annually, and subtract it from the group employee to the available time on the specified project task. You may have subtracted vacation time, time and other time in the average, and the same processing is also processed for training time.
14. Record your estimation and how you achieve estimates
When you are ready to estimate the work, you record them and record how you complete each task. Understand the assumptions and methods used to create estimates, making them easier for protection and adjustments when necessary, and it will help you improve your estimation process.
15. Record the estimation and use the estimation tool
There are a lot of business tools to help you estimate the entire project. These tools can give you a possible schedule for you, based on their real project experience. They can also help you avoid the "impossible area", that is, the product size, group size, and progress arrangement have no known project success. Software Productivity Center (www.spc.ca) The company's Estimate Pro is a tool for a trial.
16. Comply with learning curves
If you try new processes, tools, or technologies in the project, you must recognize the cost of paying short-term productivity reduction. Don't expect to get amazing benefits in the first attempt of the new software engineering method, consider inevitable learning curves in progress arrangements.
17. Consider accidental buffering
Things will not be as accurate as the project plan, so your budget and schedule should include some unexpected buffers to accommodate unpredictable events at major phases. Unfortunately, your administrator or customer may use these buffers as fillers, rather than sensible recognition facts. Indicates that some unexpected accidents are unpleasant, and you will understand your deep.
18 Record the actual increasing situation and estimation If you don't record actual working hours spending on each task, you will never improve your estimation. Your estimation will always be guess.
19 Only when the task is 100% complete. Only the task is completed
One advantage of small round stone using inch size is that you can distinguish whether each small task is either completed, or not, this is much more than the estimated a big task. Don't let people only have the completion of their tasks; use clear criteria to determine if a step is true.
20. Open, fairly tracking project status
Create a good atmosphere, let the project members feel safe about the status of the project accurately. Strive to make the project on the exact, data-based facts, rather than the misunderstanding optimism caused by fear of reporting messages. Use the project status information to correct the operation when necessary, and praise when the conditions are allowed.
These tips can not guarantee your success, but it will help you get a solid handle on your project, and to ensure that you can do what you can do, you can success in this crazy world.
