User talk:Steven 0524

2001ICT Project Management Group Assignment 2

Version 1.0

Introduction
''This Section of the Plan introduces the Project. It should contain the following elements:''

Project Overview
''A brief statement containing a formal identification of the Client and the client contact; a list of the members of the Team; a statement of the project objectives and a description of the problem that the project addresses, and the key milestones for the project. The relationship (if any) between the project and other projects should be stated.''

Project Deliverables
''A list of the items to be delivered to the project client on completion of the project. ''

Evolution of the Project Management Plan
A description of the procedures to be followed for maintenance of the information detailed in the Plan, and for maintenance of the work breakdown structures, estimates and schedules in the event of changes, whether scheduled or unscheduled, to the project.

Reference Materials
''A complete list of all documents and other sources of information referenced in the Project Plan. This section may identify other planning documents regarded as important; references to these plans should clearly identify the content required. All documents referenced should be cited using an appropriate bibliographic style. ''

Definitions and Acronyms
''A list of all terms and acronyms necessary to understand the Project Plan. ''

Project Organisation
''This section of the Plan sets out the way in which the project is organised. It should contain the following elements: ''

Software Life Cycle Model
''A description of the life cycle processes to be employed for the Project. This should include an identification of, and justification for, the selected software life cycle, the nature and extent of selected tailoring, together with an identification of the relationships between the major project functions. A combination of graphical and textual means can be used for this description. The process model should be based upon a tailoring of the processes from ISO/IEC 12207.''

Organisational Structure
''A description of the internal management structure of the project. This should include the definition of the primary roles to be employed in the project, and of the lines of communication and authority. ''

Organisational Boundaries and Interfaces
''A description of the relationship between the project team and the other parties involved in the project. Relevant stakeholders in the Project should be explicitly identified.''

Project Responsibilities
''An identification of specific responsibilities associated with each of the identified roles in the Project Team. ''

Managerial Process
''This section of the Plan describes how the project will be managed. It should include the following elements:''

Managerial Objectives and Priorities
''A description of the philosophy, goals and priorities for management activities during the project. This will include mechanisms for communications and reporting; relative priorities among the different objectives of the project; and means for resolving interpersonal issues within the team.

Assumptions, Dependencies and Constraints
''A description of the assumptions on which the project is based, the external events on which it is dependent, and the constraints under which the project is to be conducted. ''

Risk Management
''A description of the risk management strategy for the project. This should cover identification of the risk factors; assessment of the possible impact and likelihood of the risks; definition of management strategies for avoiding and containing risk; and means for ongoing monitoring of the risk factors. ''

Monitoring and Controlling Mechanisms
''A description of the methods to be used for monitoring progress and controlling the project. Project progress should be tracked by recording completion of deliverables. The tracking process must be described. In particular, this section of the plan will define the measurements to be collected that will permit effective tracking of project progress, goals and risks.''

Staffing Plan
''A description of the skill needs for the project and the means to be employed to satisfy these needs. While the total staff resources available to this project are fixed and constant, the skill requirements are not; strategies will need to be identified to meet the specific needs of each project.''

Technical Process
''This section of the Plan describes what tools, methods and techniques will be used in the Project, and how their use will be documented. It should include the following elements:

Methods, Tools and Techniques
A description of the methods, tools and techniques to be used to achieve the project objectives. This section will reference the technical references and standards used for application of the Primary Processes. There will also be a cross-reference to relevant sections of the Quality Plan.''

Work Product Documentation
''A definition of the documentation requirements for the project. This Section of the Plan should define the documents to be prepared, and set out the standards for document format and presentation.''

Project Support Functions
''Descriptions of and references to the documentation of relevant project support processes. The support functions should include:''

Quality Management
''An outline of the specific quality objectives for the project, and of the quality management strategy to be applied. This should be brief, and may refer to a Quality Plan that will be developed separately; it should identify the processes relevant to quality management that will be implemented, and how these relate to the overall process model and life cycle for the project.''

Verification and Validation
''An outline of the strategy for verification and validation to be applied. This should be brief, and may refer to other plans that will be developed separately; it should identify the processes relevant to verification and validation that will be implemented, and how these relate to the overall process model and life cycle for the project.''

Configuration Management
''An outline of the strategy for configuration management to be applied. This should be brief, and may refer to a Configuration Management Plan that will be developed separately; it should identify the processes relevant to configuration management and change control that will be implemented, and how these relate to the overall process model and life cycle for the project.''

Work Packages, Schedule, and Budget
''This section of the Plan documents the Work Breakdown Structure, dependencies, resource estimates and schedule for the Project. Much of this material can be generated using automated tools, and supplied as appendices to the Plan itself. Changes to the Plan will necessitate changes to this material, and the means for evolving the plan needs to be covered in Section 1 of the Plan. This section of the Plan should contain the following elements: ''

Work Packages and Dependencies
''A work breakdown structure must be documented, and task dependencies must be shown clearly. The WBS must be based upon and derived from ISO/IEC 12207.''

Resource Requirements and Allocation
''The procedure for estimating resource requirements must be documented. A top level estimate of size for the project as a whole, based upon a functional size measurement approach, must be generated and used a a basis for defining estimates for effort and duration. Estimates for the activities and tasks listed in the WBS must be documented and justified. The allocation of resources to the tasks must be clear and unambiguous, so that any overloading of specific resources can be identified.''

Schedule
''The Schedule should show, in graphical or textual form, the planned starting and finishing dates of each task listed. The critical path showing the minimal set of tasks for successful project completion should be clearly shown. There must be provision for the schedule to be updated following changes to the Plan.''