"Software Project Management" Reading Summary 2- Software Project Implementation Step-by-Step Method

1. Identify project goals and scope

   1. Identify goals and effective metrics
      1. Goal: What is the result to be completed and delivered?
      2. Effective measurement: What is the bottom line of delivery? What are the deliverables? Goals should be clear, specific and measurable.
   2. Establish the person in charge of the project
      1. The project has full authority to operate and the person in charge, someone has to make a decision, someone has the responsibility, and someone has the final say.
   3. Identify stakeholders
      1. Inside the user, outside the user
      2. For users with multiple interests, a representative committee can be established to determine the specific spokesperson for specific interests.
   4. Synthesize the above and modify the project goal
      1. It is not a step that must be carried out specifically, but according to the above synthesis, adjustments will be made during the project.
   5. Determine the relationship and communication methods of each department
      1. For large projects involving multiple departments, the settlement process between departments is also critical.

2. Identify target basic requirements

   1. Establish the relationship between the project and strategic planning
      1. Projects are also part of the company’s development strategy. Learn to accumulate in projects
   2. Mark installation standards and regulations
      1. Documents, development and implementation processes must have clear standards, executable, reproducible, and recorded, so that they are easy to learn and take over.
   3. Indicates the organizational structure of the project team
      1. If it is a large company involving multiple departments involved in project development, then it is also necessary to sort out the organizational structure of each relevant department of the project team.

3. Analyze project characteristics

   1. Identify how the project is driven
      1. Product-driven or goal-driven? Different driving methods should adopt different implementation methods for management.
   2. Identify the high-level risks of the project
      1. During project implementation, the risk factors that directly lead to project failure need to be focused on.
   3. Consider user needs for the project
      1. User's preference and habit of technology
   4. Select development method and life cycle method
      1. Waterfall model etc.
   5. Review the overall resource estimate
      1. Overall resources to support the project

4. Identify target products and activities

   1. Identify and describe the product of the project (what is delivered?)
      1. Including manuals, tools, documents, codes, etc. produced by the product and its affiliates.
   2. Documented common product flow
      1. Achievement relationship between product stages
      2. PFD product flow chart
   3. Make an ideal activity network diagram
      1. The work in the production process of the product, on the basis of PSD, refine the work content of each product
   4. Modify the ideal activity network according to the needs of the stage and checkpoint
      1. According to the time node and project needs, the above process time nodes can be flexibly grasped.

5. Estimate the workload of each activity

   1. Bottom-up estimate
      1. Distinguish the difference between time-consuming and workload
      2. The workload of individual activities should be integrated from the bottom up with the overall plan
      3. Indicate the time spent on the activities in the activity network diagram
   2. Modify the controllable activities created by planning
      1. The time period of some individual activities may be too long, so the task needs to be broken down and detailed to make the project more controllable and more appraised.
      2. Combined with management needs, such as a project progress meeting every two weeks, it is more appropriate to schedule the activity plan for two weeks.
      3. Many important tasks only need a short period of time, so we want to pack these and form a checklist to ensure that these tasks are enough to attract attention.

6. Identify risk

   1. Identify and quantify activity-based risks
      1. Refine to the potential risks of success for each activity and subtask
      2. For the content that cannot be accurately estimated, use the time range method to control
      3. Project task arrangements are based on premises and assumptions, and further analysis is carried out in conjunction with relevant content
   2. Plan appropriate risk measures
      1. Risk prevention plan
   3. Adjust the plan according to risk
      1. Make some adjustments to the original plan based on risk analysis

7. resource allocation

   1. Sort out the resources on hand and the resources needed

   2. Modify plans and manage tasks based on resources
      1. Gantt chart

8. Review/release plan

   1. Review project plan quality
      1. Evaluate whether the project is really completed
   2. Documented comments
      1. Solicit opinions from stakeholders on the premise that they understand the importance and relevance of the project

9. Execute the plan and carry out the lower-level planning process