Software Project Management Program

Apr 21 posted in Development (RSS), comments.

Software Project Management Program
1 Introduction
1. The preparation of the purpose of
Description of the project specification of flow management programs, including the startup process, planning process, implementation process, control process, the end of the process of scientific management control. Covers nine areas of project management: overall management, scope management, time management, cost management, quality management, human resources management, communication management, risk management, procurement management.
The reader is expected to: Project Manager, the demand for designers, systems analysts and programmers

Two project management process
1. Startup process
Analysis of personnel system must be based on scientific methods to implement the project needs analysis, select the program to develop good projects, strict screening and feasibility analysis and research, such as text
File.
2. The planning process
In the course of the project plan, we should plan to respond to change, specific preventive measures and remedial measures, development of project standards and rules and regulations, to avoid the plan is not now
It is impractical, cumbersome, etc. may result in invalid and project plans and other factors out of control.
1. Project Manager in accordance with needs analysis to make the project cost estimates, the progress of the budget, the definition of project quality standards, the risk of organizations and projects such as General Plan requires the project
Control and enforcement personnel must be highly specific project objectives, determine the scope of the project and to the target with the project stakeholders (clients) to obtain consensus;
2. And project organizations (development team) on the targets to communication, along with implementation of the project to develop the objectives of the specific plans and integration plans, and successfully
The completion of goals should be doing to reach a consensus.
3. The definition of detailed implementation schedule Gantt charts, task assignment matrix, resource planning allocation map;
4. Put the planning process leading to the company, and detailed reporting; obtain project plan approval.
3. The implementation process
1 implementation of the project to mobilize the General Assembly, the release of project information;
2 analysis and design process models, requirements modeling, a unified programming model, the model must be closely linked with reality;
3 real-time tracking of project progress, implementation of a phased evaluation, strict compliance with the project development criteria (1 phased plan Strict life cycle management, insist Jin 2
Line stage of review, strict 3 Product control, 4 to adopt the procedures of modern sophisticated design techniques, 5 the results of the review should be able to clear, 6 development team
Should Fewer but Better, 7 admit the continuous improvement of the need for software engineering practice);
4. Control process
Control and implementation of projects at the same time period, project control to follow the following points:
Customer demand for control of one
In the project implementation process, there may be changes in customer demand, may be best to control the situation, and customers to communicate, to find competent
Appropriate solutions;
2 staff management control
On the mission to track and avoid "gold-plated", the so-called gold-plated project developers are subconsciously want to do more perfect authorization procedures to increase functionality, knot
Fruit led to the expansion of the scope and demand from, or are developers intent mission, such as misunderstanding questions.
Enhance communication between staff, the timely reporting of problems to avoid the difficult combination of each module, between the problems go on, leading to job stop
Hysteresis.
Technical experience for different programmers to arrange the relevance of a strong job, and fully authorized by the project team members, to encourage the project team has completed a number of challenges
Work, enhance the development of skills, encouraged by the development of staff morale.
Use of resources histogram reaction developers working hours reasonable.
3 Project Control Management
Costs, objectives, progress for the project management of the core, must be based on strict Record icon or other means to statistical cost, objectives, progress, according to EC
SWOT analysis of data through the decision tree to be the best option, always early warning of risk response measures.
Of test data to back up.
5. The end of the process
Project preparation is scheduled to end more time to plan a more orderly, the project information and development data for after the proper preservation of Kam.
Integration testing and debugging must have test data report.
Developers to do all those involved in the project summary.

Three project management (terminology explanation)
Overall management (Intergration Management)
1. Project Charter (Porject Charter)
Project charter is a document officially launched the project, a clear objective of the project, the general feasibility study report issued by the senior management, as project
The basis for official launch.
2. The scope of the project specification (Scope Statement)
Book a clear scope of the project scope of the project.
3. Project Management Plan (Project Management Plan)
Project Management Plan are clear "how to complete the project," a collection of documents, including multiple sub-plan documents, such as: the development of milestones, quality plan
And so on.
4. Brain Storm (Brain Storm)
Project planning is a method of brainstorming, organizing team members in the conference room to discuss the issue of opening up thinking to tackle the problem or what
Project activity, it is necessary to collect data for processing.
At issue is not specific solutions or a variety of potential programs exist, they can use brainstorming.
5. Preventive measures and remedial measures (prevent measure & remedial measures)
Preventive measures and remedial measures against the problem of defects, to prevent in the first place, remedial measures can also be sometimes called corrective measures. One is a positive line
For One is a passive act.
6. Standards and rules and regulations (Standards & Rules And Regulations)
Standards are at repetitive activities constitute the best rules, sometimes it is optional, are not necessarily enforceable.
Rules and regulations are mandatory for the rules are enforced.
Scope Management (Range Management)
1. WBS (Work Breakdown Structure, WBS)
WBS Project Management are an important element in the work of the project are further broken down into projects and the entire scope of the definition.
2. Responsibility assignment matrix (Responsibiity Assign Martrix, RAM)
Distribution of responsibilities are put WBS matrix of the department or job and duty of the people linked to a chart, mainly used for job allocation.
Time Management (Time Management)
1. Milestone (Milestone) and a milestone chart (Milestone Chart)
Milestone in the project are the key points are completed analysis, the core module coding system testing completed or are completed in time.
2. Gantt (Gantt Chart)
Also known as Gantt Bar Chart (Bar Chart), with Bar, said the main activity or phase of the start and end times. Containing more than a milestone in the letter
Interest rates can be used to make the progress of plans to review and confirm, can also be used with higher-level communication between the client and reporting.
3. Project Network Diagram (Network Chart)
Project network diagram activity are detailed arrangements, including before and after the activity and dependence between the relations, the general single-arrow network (PDM) and dual-code Net
Network map (ADM) to express. Is the difference between the two: PDM framework used to express activity, using the arrow line connecting activity; ADM express line with arrows and Events
Nodes at its connecting.
4. Critical Path (Critical Path)
At the project schedule or network diagram, many routes exist to the end of the project, one of the longest route known as the critical path.
5. The progress of the progress of compression and compression method (Progress Compression)
Delay the progress of the project, it is necessary to carry out the progress of compression to speed up the progress of projects. The progress of compression is divided into two ways, first, to speed up the works (Crashin
g), the other is the rapid follow-up (Fast Tracking).
Cost Management (Cost Management)
1. Cost Estimation (Cost Estimating)
Cost estimate is the cost of each activity, based on past historical data, the use of mathematical or statistical techniques are.
Activity cost estimate accuracy according to different necessary. At the initial stage of the project, are rough, perhaps the; to more detailed planning stage; to
Allocation of costs to accurately estimate the time required.
Cost estimation methods have analog estimation and bottom-up estimates. Analog estimate is based on similar projects over the last activity for the reference, the bottom-up
Estimates by a single activity or WBS element to conduct an independent estimate, respectively, then a higher level of aggregate estimates.
2. The cost of the budget (Cost Budgeting)
Cost estimates are a single program activity or job cost package summary, the overall cost. The outcome of the budget is to be a benchmark
Costs.
3. Earned Value Management (Earned Value)
Progress or the costs are in fact not according to plan, with projects in progress will have to delay or cost overruns. Only know that scheme
Value, actual value is not enough, impossible to assess the status of the project, because they do not know how many actually completed. For example, while the cost at the time
Overruns, but a lot of work ahead of schedule, we are not sure this is a bad thing.
General consideration of the plan value (PV), the actual value of (AC) and Earned Value (EV), Earned Value Management is the basic idea.
The cost of deviation (CV) = Earned Value - Actual value = EV-AC
The progress of deviation (SV) = Earned Value - Plan value = EV-PV
Quality Management (Quality management)
1. Statistical sampling (Statistical sampling)
Statistical sampling are extracted from the target groups are part of or all the samples for inspection, in order to obtain quality data.
2. Causality Diagram (Causal map)
Causal map is an icon on the quality of statistical techniques, also known as Ishikawa diagram or fish bone diagram, the quality of questions used to analyze the causes of or deviation,
Comparison of visual display of the various factors and potential problems and results of the relationship between.
3. Pareto chart (Pareto plans)
Pareto Chart is also the quality of statistics icon technology, are in accordance with the frequency of the size of the order of drawing the histogram that the number of results are confirmed by
Causes.
Pareto Chart Pareto law of the same strain, that is, a relatively small number of factors are causing the vast majority of the cause of the problem, namely the principle of 82, 80% of the questions are
From 20% of causes.
Human Resources Management (Human Resources Management)
1. Resource histogram (Resources histogram)
Histogram of the use of resources that the project was the use of resources, use it to reaction time staff job.
2. Conflict and conflict management (Conflict management)
Projects exist conflicts are normal, common sources of conflict, including a shortage of resources, organization of work and working style.
There is a variety of strategies to resolve conflicts, the general will "lose - lose", "lose - win" and "win-win" strategy.
Communication Management (Communication management)
Risk Management (Risk Management)
1. SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
Strengths, weaknesses, opportunities and threats analysis, are specific things or risk multi-angle, a full range of trade-offs.
2. Decision tree (Decision Tree)
Decision tree is a decision support techniques, the different branches of the decision-making at the chart drawn up unified consideration. According to "expected return"
And the "possibility" of the product to be a branch of the decision-making value, then the accumulated branch decision-making should be the best decision-making.
3. The risk of response measures (Risk of response measures)
Based on risk type, the probability and impact of different customization necessary to deal with the risk strategy, risk coping strategies often have to circumvent, shift and reduce the 3
Kinds of measures.
Risk aversion means to take measures to avoid risks, such as the development progress of a very tight, can not be completed on time and circumstances, to reduce the program or system are
Of its function is to risk aversion moves.
Put the risk of transfer of risks are transferred to a third party, not to eliminate it, such as risk insurance is a typical shift.
Means to mitigate the risk of early measures to reduce the risk to receive the scope, such as through field visits, select a reliable outsourcing side, or
Through prototype demonstration system can reduce the unknown risks.
Purchasing management (Procurement Management)
1. Procurement documents (Procurement documents)
Procurement documents are issued by the buyer on outsourcing product requirements to obtain the seller's quotation or proposal. Procurement documents at different constant
The field of industry or have a specific vocabulary, have invitations to bid (IFB), request for proposals (RFP), Request For Quote book (RFQ), tender and negotiate
The invitation and so on.
2. Recommendation (Recommendation)
Proposals are drawn up by the seller paper on the seller of goods or services provided by the ability or willingness of procurement documents are answered, "subscript
Book "is a recommended book.