Cmme for development Reading Notes-Project Planning (PP)

2. Project Planning (PP) 2.1. Build estimated value

Estimated project scope

First, we will give a general description of the work project, and then establish a work splitting structure (WBS ). WBS is a term composed of three key elements: Work, a task that can generate tangible results, and breakdown, a hierarchical structure of progressive subdivision and classification; structure: Organizes parts according to certain patterns.

 

Establishes the estimation of work product and work project attributes

The following types of work products are available:

• Runable software products andSource code
• Documents and Archives

 

The following methods are used to measure the scale:

• Features
• Number of original code lines (sloc)
• Number of classes and objects
• Number and complexity of interfaces
• Document pages

 

Define the project lifecycle

The definition of each stage of the project life cycle depends on the scope of requirements, estimation of project resources, and the nature of the project. Generally, the project lifecycle is divided into four stages: "identifying requirements, proposing solutions, executing projects, and ending projects.

 

Estimate workload and cost

The estimated workload and cost are generally calculated based on the model analysis results or historical data applied to the scale, activity, and other planning parameters.

2.2. Development Project Plan

Establish budget and progress

The project budget and progress should be arranged based on the developed estimated values, and the dependencies between budget allocation, work complexity, and work projects should be properly considered.

 

Identify project risks

This mainly includes identifying risks, recording risks, reviewing the integrity and correctness of recorded risks with relevant stakeholders, obtaining their consent, and appropriately revising risks.

Risk identification and analysis tools include: risk classification, risk evaluation, checking table, structured interview, brainstorming, performance model, cost model, network analysis, and quality factor analysis.

 

Planning Data Management

Establish data privacy and security requirements andProgramNot everyone has the need or permission to access project data. A program must be established to identify who can access what data at what time.

Establish a mechanism for storing and using stored data. The information used should be expressed in an easy-to-understand type (for example, an electronic type or a computer output from a database, or it is expressed in its original form.

Determine the project materials to be identified, collected, and distributed.

 

Plan project resources

1. Determine process requirements

2. Determine the employment requirements

3. determine the demand for facilities, equipment and components.

 

Knowledge and skills required for planning

1. Identify the knowledge and skills required to execute the project.

2. evaluate available knowledge and skills.

3. Select a mechanism to provide the required knowledge and skills.

4. Integrate the selected mechanism into the project plan.

 

Planning stakeholder participation

Each major activity of the project should identify the stakeholders affected by the activity and the stakeholders with project technologies to guide the activity.

 

Create a project plan

The project plan defines all levels of manpower in a logical way; project life cycle considerations; technology and management; budget and progress; milestones; data management, risk identification, resource and technology requirements, and identification and interaction of stakeholders. The infrastructure description includes the relationship between responsibility and authorization between project members, the support of the Management class and the organization.

 

2.3. Make a commitment to the plan

Review plans of affected projects

All plans that affect the project should be reviewed to ensure consensus on the scope, objectives, roles and relationships required for project success.

 

Adjust work and resource levels

The adjustment methods include: reduce or delay the demand for technical efficiency, seek more resources, find ways to increase productivity, delegate and adjust the skill mix of project personnel, and revise all plans or schedules that affect the project.

 

Plan commitment

Generally, a temporary commitment is more appropriate to allow work to start and conduct relevant research. A sufficient commitment is required when confidence increases to an appropriate level.

2.4. thoughts and experiences

I learned the project planning chapter in CMMI and extracted some content from it. In general, there are still some successes according to his requirements. InArticleIt divides project planning into three parts: Creating estimates, developing project plans, and making commitments to the plans. In the actual implementation process, there will be many difficulties. First, the establishment of the estimated value in the document is based on the premise that the requirements are clear, in software development, the demand is often the least easy to grasp. How can we effectively grasp the demand? If the demand cannot be grasped, it is estimated that it is just a bit confusing and beautiful. In addition, the measurement method also compares the number of faulty lines of the original code (sloc), the number of classes and objects, the number and complexity of interfaces, and the number of document pages. It is difficult to estimate these items, another estimate is that workload and cost are not the main factors. The promise of the Plan will be difficult in reality. There is a risk of the software itself, because the promised person is indeed not sure to complete it during this time. The other is responsibility, office politics, and the boss's vision is different from that of employees.