Project Plan Summary

 

Project objectives:It includes three objectives: progress, cost, and quality. the cost is mainly the input of human resources. the quality goal should generally be the leakage of defects after the product enters the maintenance phase. the process requirements of the project, and the quality requirements of the relevant artifacts in each stage of design and development. these three elements are the main objectives of the project, and other objectives may exist. if you need to control the scope of changes in the project, you need to control the level of personnel skills during the project process, and the deviations you have defined for each process. the entire project management process and stage activities are carried out around the relevant objectives, and the project is completed on time and quality with limited resources. Assumptions and constraints:The biggest difference between assumptions and constraints is that one is definite and the other is uncertain. assume that the most important thing is to provide a basis, which affects the implementation of the project planning process and project objectives. However, based on the currently known factors of the project, it cannot be determined whether the basis is certain. the constraint is that this basis must be established, and the project must follow this basis. the following example assumes that the coding personnel can be in place after the project enters the design and development stage, and that the range Deviation during project execution will not exceed 10%, assume that the historical estimation data based on project estimation is authentic and credible. we also consider constraints from several factors of the project, from Progress, resources and quality. technical constraints should also be taken into account, such as the development tools used by the project, technical architecture, and technical standards that must be followed. for example, if a project must use a ** standard development webpage to meet the browsing requirements of different browsers, the project resource is restricted to ** persons, and the project version must be released on ** day. Project Acceptance Criteria:This is an important basis for project closure. When the project ends, the project acceptance must pass the project acceptance criteria to prevent the competition. project outputs are products, services, and results. clear acceptance criteria and standards must be defined for each item. therefore, project deliverables must be verifiable. If they are unverifiable, they cannot be called project deliverables. Roles and responsibilities:This must be clearly divided. Generally, there is only one responsibility and role, but it can assume tasks with multiple roles. there is a many-to-many relationship between roles and responsibilities. for example, a reviewer is a virtual role and may not have such a role. however, requirements, design, development, or testing personnel can all serve as reviewers. Project custom process:An important concept of cmme Level 3: A project should define its own process based on the standard process at the organizational level, and relevant cropping standards can be defined at the organizational level, you can crop a custom project based on the cropping standard. due to the control problem of multi-process or output controls, it is generally not recommended to use agile or iterative methodology or lifecycle model for CMMs. Now there is a dedicated agile CMMS, which is an important topic of research. Milestones and baseline:The milestone is to summarize and review the work of the previous stage, confirm whether the deliverables of the stage meet the requirements and quality standards, and confirm whether they can enter the work of the next stage. the total milestone duration is zero. after a milestone is reached and approved, you can baseline all deliverables of the milestone. The baseline is intended for configuration items, and the baseline is designed to ensure the consistency of work products, the baseline work product serves as the input and basis for the next phase of activities and tasks. Project methods, tools, technologies and standards:These factors are important project elements, which are more emphasized in Agile Methodology or agile project management. when the resources and progress of a project can meet the needs of the project, the failure is often caused by a problem in the selection of methods, tools or technologies. Estimation:The workload deviation or scale deviation allowed by the project is generally about 20-30%, while the progress deviation is generally stricter. Therefore, it is best to make an estimation accuracy of more than 80%, if the estimation is inaccurate, the progress plan will be adjusted frequently in the future. project management or planning is an incremental process. Therefore, it is best to make an estimation twice. After the software requirements are met, make another estimation to estimate the design and development workload accurately. because the estimation items of function points cannot correspond to the final activities and tasks, the EIF and Ilf of the estimated data functions cannot be decomposed into the transaction functions, therefore, I personally think that estimation of Function Points is more suitable for an estimation of the total project scale. obtain a credible project cycle data based on the total scale/productivity. the expert method and the three-point method are our common estimation methods. The three-point method can be used to calculate the most possible estimation value and obtain the estimated range data of a project cycle. Schedule:Next, let's talk about the sequence. First, we need to determine the scope, select the project lifecycle model, and then conduct top-layer WBS decomposition to estimate the size of the decomposed WBS, calculate the relevant workload data based on historical productivity data. determine relevant activities and tasks based on WBS, sort activities and establish dependencies, determine the project role responsibility matrix and resource allocation criteria, and arrange resources for the activities according to the rules, draw a network diagram to determine the key resources and key paths, schedule and balance the resources. when assigning resources to a task, ensure that the key resources are allocated to the key task first. When the key resources undertake multiple tasks, a general principle is: Set A1, b1 is two key tasks. A's subsequent dependent tasks are A2, and B1's subsequent dependent tasks are B2. A1 can start three days earlier than B1, and the key path from A2 to termination is L1, the key path from B2 to the end is L2.
A. When the two key paths counted from the subsequent tasks are about the same, the key resources can first start the tasks in advance. That is, the A1 task is started first.
B. When L1 is more than three days shorter than L2, the B1 task should be given priority at this time, although it is important to idle key resources at this time. Personnel Plan:The most important thing is the phased-out staff input plan. for software development projects, you only need to invest 20-30% of the personnel in the demand and overall design phases. therefore, the personnel plan should be a phased-out plan. the input personnel must specify the relevant skill requirements and evaluate the skills of the project personnel after the skill requirements are defined. If the skills of the project members do not meet the requirements, they must develop relevant training plans, track the training effect and track and control the risks included in the project. Personnel skills:Generally, developers should have at least 1-2 years of work experience, which should be a basic requirement. A higher IQ, a better basic theory, and a period of practical knowledge cannot be converted into skills. however, after one to two years, work experience and skills have a non-linear relationship. It doesn't mean that your work experience is long and your skill level is high, this is related to personal, environment, and many other factors. if you have worked for 5 or 8 years, you may be able to reach the expert level. Risk plan:Risk management is an important part of project management. The risk management process runs through the entire project lifecycle. In the risk management plan, the risk management team members and their respective responsibilities should be determined first. For PDM projects, the risk management team owner is the project manager. after the risk team confirms, it is necessary to determine the tools and methods required in the risk management process. This includes risk identification, risk analysis, risk monitoring, and risk response. These methods and tools have clear definitions and guiding principles at the organization level. You should select the appropriate method based on the actual situation of the project when there are multiple methods. There are clear standards and definitions for the source and classification of project risks at the organizational level, which can be directly used by projects, however, you may need to crop the project based on actual conditions. If the project itself cannot have procurement risks, you need to crop them so that you do not have to think too much about risk identification and analysis in the future.
The risk response policies in the Project Plan are not specific to a specific risk. Therefore, the response policies here are more generic response policies, such as development prototype, Skill Evaluation and Training, and data simulation. When encountering actual risks, how to deal with them should also be analyzed based on the actual situation of risks. In the project planning phase, all risks under the current condition of the project should be analyzed and the risks should be sorted in priority. After the project is identified as a key risk, the risk mitigation plan and response measures need to be developed, which must be reflected in the progress plan. The progress plan must contain such content as a complete progress plan. When we have accumulated enough historical data, we can perform combined analysis and quantitative analysis on risks. For risk quantitative analysis, we can use decision tree and Monte Carlo simulation methods. For details, refer to the following documents. Quality Plan:The quality plan to be implemented in the Project Plan and the quality assurance plan to be prepared by QA are completely different. the QA quality assurance plan focuses on the review of processes and artifacts to ensure that the project complies with the plan and process execution. in the project plan, the quality plan tends to focus more on the product quality and the control measures to achieve the product quality. the source and user requirements for quality objectives come from at least the quality improvement requirements of the project and from the experience of historical projects. Therefore, we should first formulate relevant quality objectives, then, the project's defect trends and number of defects in each stage are estimated based on the quality objectives. In order to achieve the quality objectives, the required review, testing, review, and other related workload are estimated. requirements on the coverage rate of review and test can be estimated based on the data. Coq, copq, and cogq