Review of Software project Management (i.)

0th Chapter Overview

In the activities of human daily life, the ability to meet these conditions can be called a project.

2. Purpose: To create a unique product or to provide a unique service

4. Dependency: There are many activities related to each other in the project.

6. Periodicity: To be completed within a certain period of time.

8. Uniqueness: To a certain extent, each project is unique.

10. Constraint: The project is constrained by resources.

12. Uncertainty: A plan should be made before the project starts, but there will always be changes to the plan due to various factors.

Examples of projects: picnic activities, collective weddings, development of Microsoft's operating system, Shenzhou spacecraft program.

Non-project activities: class, community security, daily hygiene cleaning.

Basic elements of the project: Technology, Methodology, team building, information, communication.

Chapter II Scope Planning WBS

Work break down structure

2. Reference method

4. Analogy method

6. Top-down: For more familiar projects

8. Bottom-up: for new projects

Topic type: give a description, draw a task decomposition

Chapter III Progress Plan

There is a dependency between tasks, and the progress of the software needs to be managed.

Progress Management Diagram Gantt chart

Cons: The dependencies between tasks cannot be clearly expressed, and critical paths, and critical tasks, are not explicitly represented.

Network Diagram

The network diagram has three kinds, PDM,ADM,CDM, the front two kinds are the emphases. PDM takes tasks as nodes, and ADM takes tasks as edges.

Project duration Estimate

A diachronic estimate is an estimate of the time it takes to complete a project.

Quota Estimation algorithm

Project Time = activity workload/(number of units per resource × amount of work per unit Time Unit Resource)

。。。 Don't explain

Engineering Review Technology PERT

This estimate calculates three estimates for the activity in each project and computes a weighted average.

O:optimistic, optimistic estimates, that is, the shortest time estimate.

P:pessimistic, pessimistic estimate, the longest time estimate.

M:most likely, the most likely completion time estimate.

The PERT estimate for the current activity is (O + 4M + P)/6. The estimated value of the entire project is the and of the estimates for all tasks.

PERT has a risk analysis problem. According to the normal distribution estimate, the probability of completion within the e±δ is 68.3%,e±2δ 95.5%,e±3δ is 99.7%.

Project Schedule Preparation

The process of determining the start and end dates of a project is often carried out concurrently with the project's diachronic estimate.

Critical Path method

2. Early Start,es, the earliest time a task can begin-means that at the earliest of this time, the task's predecessor was finished.

4. Late Start,ls, on the contrary, this time, the mission's precursor must be over.

6. Early Finish,ef, optimistic estimated completion time

8. Late FINISH,LF, pessimistic estimated completion time

10. Lead,lag ""

12. float, float ""

14. Critical path, the ES = LS task is called mission Critical, and a series of key tasks on different task chains are linked into critical paths. On the network diagram, the critical path is the longest path that floats to 0.

Examples of P75 (Fig. 3-16) illustrate these nouns.

The ES,LS,EF,LF of the computational task uses both forward and inverse methods (p75-p78).

Time Compression method

Emergency method and parallel operation method

Resource Balance Method

The critical path method can generate a schedule, but often the plan requires too much resources. The resource balance method generates the project plan under the condition of resource constraint.

Fourth project cost plan

A review of 4.3.7 estimation methods first reading

1. Lines of code, function points, and object points

The function point progression (UFC) and technical complexity factor (TCF) are not adjusted.

2. analogy estimation

3. bottom-up estimation

4. parameter model estimation

Review of software project Management (i)