Guideline: Important Decisions in Project Management








var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_4U33kAILEdq-_NKqZM1EhA", "_nB0hwAITEdqu-LkyOdB8SQ", "_yeA1y9nmEdmO6L4XMImrsA", "1.1488032793761973E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_kC0pcN7GEdm8G6yT7-Wdqw", "_yeA1y9nmEdmO6L4XMImrsA", "1.1488032793761973E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_2ClPcDIcEdqDs_9ORT1Rig", "1.1488032793761973E-305"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Guideline: Important Decisions in Project Management















This guideline describes important things to consider when tailoring the Project Management aspects of the process.






Relationships



Related Elements


Project Management


Project Management


Tailor the Development Process for the Project






Main Description



Decide How to Use Work Products Make a decision about what work products are to be used and how they are to be used.  In addition to identifying what work products are to be used, it is also important to also tailor each work product to be used to fit the needs of the project.  The table below specifies which Project Management work products are recommended and which are considered optional (i.e., may only be used in certain cases). For additional tailoring considerations, see the tailoring section of the work product description page. Work Product Purpose Tailoring (Optional, Recommended) Business Case Used to determine whether or not the project is worth investing in. Recommended. Iteration Assessment Captures the result of an iteration, the degree to which the evaluation criteria were met, lessons learned, and changes to be done. Recommended. Iteration Plan The detailed plan for the iteration, including the time-sequence of tasks and resources. Recommended. Software Development Plan including, usually:  Measurement Plan  Problem Resolution Plan  Product Acceptance Plan  Quality Assurance Plan  Risk Management Plan Includes all information required to manage the project. All projects need some planning in order to manage a project. Smaller, less complex projects, may have a single document capturing the project plan. Larger, more complex, or more formal projects will require multiple separate subplans.  Project Measurements This is the repository of all measurements related to the project. Recommended for most projects. On many projects, only a few measures are used, such as cost and progress measures. A metrics database is required only when there is large amount of metrics data to be managed. Many organizations gather metrics data from multiple projects in order to glean information to apply to future projects. Review Record Captures the results of a review of one or more project work products. Review records can avoid misunderstandings of decisions made during a review. They also serve as evidence to stakeholders that project work products are being reviewed. Recommended for most projects. Most projects will want to record decisions made in meetings with the customer and other key stakeholders, in order to ensure a common understanding. Reviews records for other reviews may or may not be formally captured, depending on the review formality applied by the particular project. Risk List This is a prioritized list of project risks. Recommended. May be just a section in the Software Development Plan. Status Assessment Used to capture a snapshot of project status, including progress, management issues, technical issues, and risks. Recommended. The Status Assessment may be combined with the Iteration Assessment if the iterations are frequent (one each month). If iterations are lengthy, there will be a need for intermediate Status Assessments. Work Order This is a negotiated agreement between the Project Manager and the staff to perform a particular task, or set of tasks, under a defined schedule and with certain work products, effort, and resource constraints. Recommended for most projects. May be implemented using Change Requests.





©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();