Schedule management
Define the activities
Break the project down into its smallest units, activities, and make a list of activities
Arrange the sequence of activities
Arrange the order of activities according to the decomposed activities, and consider the dependencies among the activities.
Estimated active resources
Estimate the resources required for the activities based on the sequence of activities listed
Estimate activity duration
Estimate the time required for the activities based on the activities listed
Make a schedule
After all of the above, make a plan based on resource estimation, world time estimation, and sequence of activities. The plan has resource requirements, project calendars, progress benchmarks
Control the progress
Hold daily station meeting, do project summary, timely communication, use project management tools, correct demand research, team building, reasonable change process
Risk management
Risk classification of software project:
Demand risk: the demand for customer understand the needs of the poor, benchmark requirements are always changing, unclear resource risk management process: the resources of low morale and changes of resources, training does not reach the designated position, the conflict between the resources, the resources of the specific skills, technical risks, technical barriers to the implementation of, the evaluation of the underground, high code quality progress Customer risk: Customers are not satisfied with the quality of delivery, customer demand has not been adopted, the customer to the planning, round review time is long, the customer response time is too long, poor business and customer communication Organizations manage risk: non-technical product manager of the project evaluation and management of the project period of temporary adjustment, management does not pay attention to the test,
Identify risks
Identify risks through brainstorming, Delphi, interviews, SWOT analysis, fishbone diagrams, flow charts, hypotheticals, etc
Perform risk analysis
Risk analysis is carried out to analyze the probability of its possible occurrence and the impact caused after the occurrence. Ranking is carried out according to the probability and impact. The analysis method is generally based on expert judgment and work experience
Planning risk response
Risk avoidance, mitigation, transfer, reporting, acceptance
Implementing risk response
Avoid changing the project plan to eliminate risk mitigation Mitigation of risks that cannot be avoided by increasing resources or by other means: risk transfer by purchasing insurance or other means to report unmanageable risks. Accept and report risks that cannot be avoided or mitigated, and make contingency plans
Control risk
Monitor the response to risks. Identify changes in risk levels. Identify new project risk assumptions
Quality management
Software quality attributes:
Comprehensible, maintainable, testable, portable, reusable, and operational robustness integrity
Planning quality management
Define standards, define methods, define quality standards for project deliverables and develop tools to be used in the quality management process, such as fishbone diagrams, cost-benefit analysis, affinity diagrams, etc. Preventive cost: the cost of preventive work to prevent the introduction of defects into the software. Evaluation cost: The cost of the effort to check whether the software contains defects. Failure cost: The cost of fixing defects.
Management of quality
Conduct quality audits during the project: identify the best practices of ongoing projects, identify all irregularities, gaps and deficiencies, and identify the causes of low quality through tools such as seven charts and check sheets. Document best practices or violations in a timely manner and contribute to the knowledge base. Take corrective actions to reduce quality cost and improve project success rate. Develop quality improvement methods and submit change requests if necessary. Defect tracking: bug tools, defect reporting, defect allocation, defect handling, defect verification
Control the quality
Review: Technical review, code review, code testing, process inspection, process improvement through inspection, testing, checklists, control charts and other tools, to ensure that the deliverables meet the quality requirements for final acceptance. Quality control can be carried out throughout the project life cycle.
Cost management
Planning cost management
Software industry is the cost of hardware and software acquisition cost Such as server, monitor, etc. Various depreciation expense Artificial cost development projects need maintenance and training of human maintenance project For new recruits training, and technology is not skilled staff training fees, travel expenses Such as saving, bidding fee, Business trip expense management and service charge related items supporting other personnel expenses
Estimated costs
Select appropriate estimation methods for estimation: analog estimation, three-point estimation, parameter estimation, bottom-up estimation based on WBS, resource requirements, resource consumption rate, schedule planning, historical project data and other methods to estimate. Considerations for cost estimation: choose appropriate estimation methods, slip out of estimation time, accumulate project data, and use appropriate estimation tools
Make budget
Develop a summary cost baseline through cost summaries, risk registers, progress plans, and reserve analysis for each activity. Reduce budget: improve development quality, use skilled resources, remove tasks, replace resources
Control the cost
Use earned value analysis, reserve analysis, etc. to monitor project cost, find out the deviation between actual cost and planned cost, find out the cause of deviation, take corrective action.
Software project scope management
Demand for
Categories of software requirements: interface requirements, functional requirements, performance requirements, quality requirements, abnormal requirements and so on. Demand collection tools: questionnaire, interview, conference, prototype method
Scope definition
Implement the project scope specification by describing functional features, system interfaces, and quality features. The project scope statement includes: description of the scope acceptance criteria description of the deliverables constraints assumptions
Create a work breakdown structure
Make the collected requirements into prototype drawings. Break down the prototype diagram into smaller, interconnected, and more manageable components. WBS is an attribute structure that defines the full scope of the project, and the lowest multiplier structure is the work package. The approach to creating WBS: Top-down
Scope of confirmation
The process of formal acceptance of deliverables is typically performed by the project sponsor or customer.
Scope of control
Establish a rigorous change management process early in the project to avoid scope creep and gold-plating as the project progresses. Perform requirements identification and analysis. Deep mining requirements, in the demand analysis stage to understand user needs thoroughly. Guide customers when they are not clear about requirements.
A project
1) Scope confirmation: Before the end of the project, review the work results and progress. After the work results and progress are confirmed, relevant personnel shall sign for confirmation. (2) Quality acceptance: Acceptance shall be carried out according to the project quality management plan and stipulated quality standards to ensure that the quality requirements are met. And request the relevant acceptance personnel to sign on the document. (3) Final account of expenses: Prepare the final account of the project according to the contract, check each final account against the contract, and finally ask all relevant parties to sign after confirmation. (4) Archiving of contract termination projects: sorting and archiving of various contracts and documents, including lessons learned, procurement contracts, outsourcing contracts and so on. (5) Post-project evaluation: Review and summarize the project through the data, benefits and process of the project, find deficiencies and areas that can be improved, and summarize experience to provide better experience for the new project.