How to develop project scope and schedule

 Project scope and progress of the development?
1.
Project objectives and scope of project or start a new version, the first thing is to confirm with users needs, the scope of the project planning. Project scope, schedule, quality and resources the balance of four elements, the user requirements and the progress of the project high priority, we often have to narrow the scope of the project, the user needs to prioritize, eliminate low-priority demand. In addition, we plan to do the project scope is an important basis Our historical experience data and a clear understanding of project characteristics, project scoping, demand you to a broader estimate, or you or to users is difficult to judge clearly committed to the resources available, you are within 3 months can complete 20 or more user functions.
formal process seems to be the first confirmation that the project scope, then WBS-> confirm the actual schedule of the project cycle, but the reality is often very difficult case, users tend to focus on the progress greater than the scope of attention on a project six months or a year can not see a specific product from the user is certainly not acceptable, so our software projects are generally carried out by iterative development of incremental versions.
other It should be stressed that the project objectives identified under the project's goals can not be simply understood as at some point in time to complete all the functions. Another important objective of the project is the project's quality goals, you need to complete this project to reach that level of quality standards, delivery BUG leak rate out of the product to control what extent such content. the quality of projects will not affect our target range, but it will affect our follow-up evaluation, testing, timing, directly affect the progress of the project.
PMBOK scope of the project had already been explicitly mentioned in the definition of another important purpose is to project performance measurement and acceptance criteria, when you deliver the project needs of the user manual based on the content of user acceptance of the project, all of our definition of the scope of the project must be clear, quantifiable, verifiable, and testable, so as to avoid unnecessary disputes later.
Also in the needs analysis phase of the project outlined in the assumptions and constraints, assumptions and constraints are divided into technical and non-technical aspects, where We analyzed all the assumptions are likely to become the project's risks.
2.
to determine progress of the project objectives and determine the scope of the project, you need to begin to determine the course of the project, the project adopted throughout the process life cycle model? whether the organization during the project definition of a standard process-level crop and other related content. project is defined as the process of decomposition of the WBS must be determined before a link, you use the waterfall model and incremental iteration model and scheduling arrangements WBS decomposition is clearly completely different.
clear during the project recognized the project's WBS after decomposition, WBS decomposition is generally the core members of the team, but the project manager should play a leading and coordinating role. WBS decomposition process and are generally based on success in two ways, but the two forms can be mixed, such as when the first high-level decomposition decomposition subsystems and work packages, while at the bottom again in accordance with the requirements, design, coding and testing process of decomposition of each. WBS the bottom of the unit of work needs to be independently verified products, need to plan and assigned tasks, work units need to have a clear responsibility of people, so sometimes when not done carefully it is difficult to estimate the unit of work to meet these requirements, so inevitable in the estimation process should be optimized and adjusted to the WBS.
WBS decomposition is complete unit of work can start the estimation of some experts estimate the general method, three-point method and function point method estimates, because our project uses expert methods estimates, and therefore need the project core members and experienced members to estimate the unit of work will normally be for the units and to estimate the complexity, and finally estimate the total size of the project, divided by the productivity of the project workload data obtained by the project . Experts estimate will generally a lot of law round, until all indicators convergence (convergence criteria determined in advance the organization or project clear, such as the deviation of difficult to estimate the specific lines of code each function encoded data and encoding of a workload, so here is the history of the project need to use empirical data, that you need to do when the history of the project: Design: what is the proportion of the workload code how? then according to the requirements phase estimated from the workload data to calculate the estimates of the design and development effort. So from this point on you can see why the software project measurement and analysis is important because you do the measurement and analysis of data As you will be an important basis for follow-up projects. a lot of projects that software estimation is not allowed to the old, reason is that you do not have your own history of the project the accumulation of empirical data.
out in the estimates, you can arrange the entire project using Project tools the progress of the plan, the arrangements in the project schedule is important in two key human resources to identify and determine the critical path. In recognition of these two factors clearly discharged after the entire project schedule is very simple. The key project Human resources can be used to determine the general unit of work -> personnel responsibility matrix to analyze the critical path for the direct use of operations research in the general critical path analysis to determine ES, EF, LE, and LF to four hours.
in project schedule can be out after the basic planning and scheduling project milestones and baselines established, the project milestones and baseline tracking control of the project important checkpoint in the landmark project will be a special milestone in the report on the current state of the project, the progress of the project, workload, size, defects and other indicators of deviation from the analysis.
out the entire project schedule, after the basic needs of all projects and project group members confirmed that internal commitment for the project, project members should be on the whole schedule arrangements for the basic agreement. project plan also needs to support programs need to be developed, the project schedule came out and configure the administrator can notify the QA quality assurance program were developed and configuration management plan, the project manager responsible to help test the system development project test plan.
3. project plan and other key factors of the project confirmed
methods, techniques, tools and standards
the project plan is an important element to be determined, namely, what to use during the project methods and techniques, using what tools, the output of all stages of the project which should meet the inspection standards. a project in addition to the commonly used development tools, will use to demand management, design modeling, configuration management, change management, IM communication, and many other tools; used object-oriented analysis and design, development language, database, testing a variety of technologies, where both need to be analyzed and clearly defined, which will be the follow-up skills assessment and training is an important basis.
Stakeholder Analysis:
all of your projects have a direct and indirect impacts of the project stakeholders are stakeholders in this project we will normally carry out the role of internal and external division of roles. In the analysis of all stakeholders clear after should also be analyzed through the responsibility matrix that all stakeholders involved in all stages of the project related activities.
skills and training of project members:
fact, this is an important part of the project plan is to on the project to assess the skills of each member, according to the project assessment results to develop training programs for the project, and tracking the effect of training. Here are common methods and tools, dependence and commitment must have a special place to record and track on a regular basis. because when you rely on the external key can not be met when the project will directly affect the progress of the whole, disrupting the pace of the entire project.

Project Risk Analysis Risk management is an important project management knowledge, CMMI assessment is a key process area. the entire project management process is ongoing to analyze, track and mitigate project risk process. Our analysis of project risks in the process of risk can make use of library , risk checklist, expert methods, brainstorming and other means. a risk include the probability of risk, consequences, the scope, duration and other aspects of treatment; risk responses are reduced, commitments, mitigation and transfer of etc.; an important part of risk analysis is to analyze the root causes of risk, and then to develop specific causes of response. risk management throughout the entire project management process that requires regular tracking of risk and re-assessment of the risk of problems for further transformed into need to pre-established contingency plans related.