23-09-2016, 02:28 PM
1455871924-spmreport.doc (Size: 389 KB / Downloads: 4)
The purpose of the Project Plan is to document all managerial aspects of a project that are required to execute it successfully within its constraints. If some aspects are defined in separate plans (e.g. Quality Assurance Plan, Configuration Management Plan, Risk Management Plan, Project Schedule), the Project Plan should refer to these documents.
It is important, that also non-applicability of a section is agreed on by the responsible manager. Therefore:
• Don’t remove headlines level 1 and level 2 headlines (Heading1 and Heading2)
• Reasons why a section is not applicable shall be documented under the respective headline
1. Overview
Help: This section describes a management summary. Provide essential information like
• What the motivation for this project is (e.g. to fill a gap in the product portfolio)
• Who the customer is
• What the project will deliver. Is it a new product or an extension of an existing one?
• What it will cost
• How long it will take
• Which organizations are involved
• Which other projects depend on the project result
• Which other projects contribute with their results
Refer to the Project Proposal [1] or other documents (e.g. Feasibility Study Report) containing information on the project background like market, technology, profitability, and competitor evaluation.
2.1 Project Goals(masood)
Help: The project goals define the expected project results together with the required development constraints. Information may be extracted from the Project Proposal [1] (or the Feasibility Study Report) and the Project Requirements Specification and completed, if required.
Identify the various categories of project goals (list the major project goals only and refer to the Project Requirements Specification or other documents for details). Consider the following categories:
• Functional goals
• Strategic goals
• Business goals (e.g.: time-to-market, cost)
• Technological goals
• Quality goals
• Organizational goals (e.g. competence development, testing of new methods, techniques, or tools, application of new processes, etc.)
• Other goals, e.g.: usability, portability, etc. (these goals, and what is specifically expected, should be clearly specified in the Project Requirements Specification)
• Constraints (e.g.: environmental constraints, application specific standards, national standards, cultural relationships, etc.)
Prioritize the project goals:
Functional, business, and quality goals should be prioritized at least.