Project planning development

Sensitivity analysis is used to identify and quantify project characteristics that are major factors in the expected value of a project/ and is one of the most powerful tools of modern portfolio management. Sensitivity analyses serve two goals. The first goal is to identify the project characteristics that were used to determine the project value/ the so-called value drivers/ and ensure that the project plan developed by the project team solidly supports these value drivers. For example/ a value driver for a potential sedative hypnotic might be that it has no potentiation or interaction with alcohol. Because much of the value of this project depends on this product characteristic/ the project team will plan to assess this expected value driver as early as possible in the development cycle. 

The project life-cycle model plays an important role in project integration management because project plan development is performed during the early phases of the project while project plan execution and project change control are performed during the other phases of the project. With a well-defined life-cycle model, it is possible to define the data, decision making, and activities required at each phase of the project fife cycle and consequently train those responsible for performing the processes adequately. 

Guide the team during project plan development and execution... 

Stage gate SGI symbolizes the project start which triggers the safety milestone SMI and the engineering milestone EMI and, therefore, starts the activities of the project start phase. The planiting activities in the project start phase irrclude project plan development and co-ordination of all involved disciplines and stake-... 

A statement of work which you require the subcontractor to perform - it might be design, development, management, or verification work and will include a list of required deliverables such as project plans, quality plans, production plans, drawings, test data, etc. You need to be clear as to the interfaces both organizationally and technically (see Part 2 Chapter 4). 

The form these end products take should be consistent with your company s style for example, if you have specific protocols for project planning or developing Standard Operating Procedures, these will probably apply to comparable tasks within the PSM initiative. 

Once you have developed the program plan and schedule, and estimated resource requirements, you should organize this information in a manageable form for presentation to your PSM sponsor. If you have kept management informed about your progress you should have a clear idea of what is expected in terms of form, content, and level of detail. A sample table of contents for a project plan appears as Figure 5-12, and Figures 5-13 and 5.14 provide additional detail on selected portions of the plan. 

Once the detailed project plan has been developed, your estimates of costs and schedule in a number of areas will have firmed up ... 

KBW [Koppers Babcock Wilcox] A coal gasification process developed jointly by the Koppers Company and Babcock Wilcox, intended to supply the synthetic fuels industry. The product is a mixture of carbon monoxide and hydrogen. Dry, powdered coal, oxygen, and steam are injected into the reactor. The reaction temperature is sufficiently high that the ash is molten it runs down the reactor walls, is tapped out as a molten slag, and is quenched in water before disposal. In 1984, seven commercial synfuels projects planned to use this process but it is not known whether any was commercialized. 

The use of appropriate reference materials should be a key feature of the quality assurance/quality control structure in any future ocean science project involving chemical measurement. Reference materials use should be explicitly addressed in the project planning stages, proposals, and publications. In the event that appropriate reference materials are not already available, the committee recommends that the proposed project develop a strategy for preparation to assure the ultimate value of measurements made as part of the research. 

Project plans and a dedicated project manager are required to coordinate across-site support activities, e.g. project planning, engineering, process development, production, QC (quality control), etc. This is critically important if production scale equipment and operating areas need to be used during the transfer exercise, i.e. the impact on commercial manufacturing schedules. 

A small but diverse team of personnel is typically involved in the activities of the Project Identification and Definition Stage (refer to Figure 2.1). Representatives from groups such as process analytics, process control, project management, central engineering and production operations should populate the team in the first stage. The size and diversity of the team should grow from the identification step to the definition step as resources are allocated and plans developed. 

For larger projects, an individual validation project plan should be developed. This plan is derived from the validation master plan. It formalizes qualification and validation and outlines what has to be done to get a specific system into compliance. For inspectors it is the first indication on the control that a laboratory has over a specific computerized system, and it also gives a first impression of the validation quality. 

Stewart, T. L., and T. M. Brouns. 1988. Waste Acid Detoxification and Reclamation Phase I - Project Planning and Concent Development. PNL-6507 and DOE/HWP-50, Pacific Northwest Laboratory, Richland, Washington. 

NASA s Mic rni ravji> Research Program Office at Marshall Center Is responsible lot the deliniuon and development of ntierogravily science and space product development projects planned for the International Space Staiion. 

Again regardless of in-house or outsource development, document a list of features and prioritize them. Break the project down into short, timeboxed iterations, each focusing on one or two of these features (Chapter 5). Do not let the iteration deadline slip. Reduce the scope of the iteration if necessary. Implement features with high business values and high business and technical risks in early iterations. Make sure each iteration delivers a production quality partial system to solicit feedback and let the system grow incrementally. The project plan should be adjusted based on the feedback. It is OK if the initial project plan is not accurate. However, it should become more and more accurate as more iterations are completed. Test and integrate early and frequently. 

---