<Name of the project> Project Plan

Project Code: <Code of the project> Document Code: <Code of the document >– v<x.x>

<Location, issued date of the Document>

<Project code>-Project Plan RECORD OF CHANGE *A - Added M - Modified D - Deleted
Effective Date Changed Items A* M, D Change Description

v<x.x>

New Version

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

2/21

<Project code>-Project Plan SIGNATURE PAGE ORIGINATOR: <Name> Project Manager <Date>

v<x.x>

REVIEWERS: <Name>

<Date>

Project Technical Leader

<Name> Division Leader

<Date>

<Name> QA

<Date>

<Name, if it’s needed> <Position>

<Date>

APPROVAL:

<Name> Group Leader

<Date>

<Name> VP OPS

<Date>

<Name, if it’s needed> <Position>

<Date>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

3/21

<Project code>-Project Plan TABLE OF CONTENTS

v<x.x>

1. PROJECT OVERVIEW................................................................6 1.1. Project description............................................. .............................6 1.2. Assumptions and constraints................................... .......................7 1.3. Project Risk........................................................... ..........................7 1.4. References................................................................... ...................7 2. PROJECT DELIVERABLES AND DEPENDENCIES...........................9 2.1. Deliverables................................................................... .................9 2.2. Critical Dependencies........................................... ..........................9 3. PROJECT LIFECYCLE...............................................................10 3.1. Stage description....................................................... ...................10 3.2. Iteration objectives............................................ ...........................11 3.3. Project schedule................................................................... .........12 4. PROCESS TAILORING/DEVIATION.............................................13

5. RESOURCE PLAN...................................................................14 5.1. Project Organization............................................................ ..........14 5.2. External interfaces......................................................... ...............15 5.3. Project communication.............................................................. ....16 5.4. Training plan.................................................... .............................16 5.5. Tools and Infrastructure................................................................ .17 5.6. Project Finance................................................................... ...........17 6. QUALITY MANAGEMENT.........................................................19 6.1. Quality objectives........................................... ..............................19 6.2. Quality activities.................................................... .......................19 7. CONFIGURATION MANAGEMENT.............................................21

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

4/21

<Project code>-Project Plan DEFINITIONS AND ACRONYMS

v<x.x>

Table 1: Definitions and Acronyms
Acronym PM PTL TL QA CC DV URD SRS ADD DDD TP TC SC CM CSCI CI PVCS VM VSS VM Definition Project Manager Project Technical Leader Team Leader Quality Assurance Officer Infrastructure Configuration Controller Developer User Requirement Document Software Requirement Specification Architecture Design Document Detail Design Document Test Plan Test Case Source Code Configuration Management Computer Software Configuration Items Configuration Item PVCS Version Manager Visual SourceSafe Version Manager Note

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

5/21

<Project code>-Project Plan

v<x.x>

1. PROJECT OVERVIEW

1.1. Project description
Project name : Project Code: Contract Type: Customer: 2nd Customer: Project level: Project rank: Group: Division: Project type: Project manager: Project category: Business domain: Application type: New development Maintenance Other External Internal Company A/B/C/D/Not rank Branch Group

< Brief description of the project which answering for questions:
Scope and Objective

What are purpose/objectives of the project What is the product, result of the project?
What is the scope of the project? (What will we do in the project?>

Committed billable effort Committed calendar effort Committed effort usage (man-month1): In which: Management activities
1

<Fil here the budgeted effort borrowing from Work Order>, in which

1 man-month equals 25 man-day

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

6/21

<Project code>-Project Plan
(%) Development activities (%) For Quality activities (%) Project start date: Planned duration: <Add here if it’s needed> Expected end date:

v<x.x>

1.2. Assumptions and constraints
1.2.1.Constraints Table 2: Constraints
No Description <Fill any constraints that apply to the project. NA if it’s not available> Type2

1.2.2.Assumptions Table 3: Assumptions
No Description <Fill assumptions that this plan is based on. Also list all key success factors for the projects. These elements have to be delivered before the project can deliver successfully. NA if it’s not available> Type3

1.3. Project Risk
<Refer to Template_Risk Assessment Matrix or Project Database if it’s not special request for filling in the Risk Assessment Matrix>

1.4. References
Table 4: Document’s References
No Document <NA if it’s not available> Issued date Source Note

2 3

These are type normally: staff, budget, equipment, schedule, infrastructure, business, ... These are type normally: staff, budget, equipment, schedule, infrastructure, business, ...

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

7/21

<Project code>-Project Plan

v<x.x>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

8/21

<Project code>-Project Plan

v<x.x>

2. PROJECT DELIVERABLES AND DEPENDENCIES

2.1. Deliverables
4

Table 5: Project deliverables to customer
Delivery location Note

No

Deliverable

Delivery date

2.2. Critical Dependencies
<Describe any dependency on other projects. In case of dependencies, describe in detail the reasons, tasks and milestones. Also include milestone information in the project plan.> Table 6: Critical dependencies
No Critical dependency Expected Delivery Date Note

4

This table and other tables in this project plan may be referred to appendixes. It’s permitted to replace tables by text but these information in table should be required.

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

9/21

<Project code>-Project Plan

v<x.x>

3. PROJECT LIFECYCLE

3.1. Stage description
<Describe here the project life cycle with defined stage. In case when some stages are merged (e.g. merge these Definition and Solution stages) it’s required to name new merged stage by combined names (e.g “Definition&Solution stage)> Table 7: Project stage summary
Stage Initiation Stage <Definition Stage> <Solution Stage> <Construction Stage> <Transition Stage> Termination Stage <1> <1> <3> <2> No. of iterations Start <Week 1> <Week 2> <Week 8> <Week 15> <Week 25> <Week 33> End <Week 1> <Week 8> <Week 15> <Week 31> <Week 32> <Week 33> Elapsed time <6 days> <36 days> <42 days> <42 days> <42 days> <6 days>

Table 8: Project stage and milestones
Stage Description <The Initiation stage will intend to get project requirements and review those, estimate project zise and effort, create the internal work order and team building.> <The Definition stage will develop the product requirements and establish the business case for the XXX System. The major use cases will be developed as well as the high level Project Plan.> <The Solution Stage will analyze the requirements and will develop the architectural prototype. At the completion of the Solution Stage all use cases selected for Release 1.0 will have completed analysis and design. In addition, high risk use cases for Release 2.0 will have been analyzed and designed. The architectural prototype will test the feasibility and performance of the architecture that is required for Release 1.0. Milestone Kick-of meeting

Initiation Stage

<Definition Stage>

<Business Case Review Milestone>

<Solution Stage>

<The Architectural Prototype Milestone marks the end of the Solution Stage. This prototype signifies verification of the major architectural components which comprise the R1.0 Release. The User-Interface Prototype Milestone enables early user feedback on the user interface.>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

10/21

<Project code>-Project Plan
Stage Description A User-Interface Prototype will also be developed.> <During the Construction Stage, remaining use cases will be analyzed and designed. The Beta version for Release 1.0 will be developed and distributed for evaluation. The implementation and test activities to support the R1.0 and R2.0 releases will be completed.> <The Transition Stage will prepare the R1.0 and R2.0 releases for distribution. It provides the required support to ensure a smooth installation including user training.> <The Termination Stage has objectives to summarize and evaluate project results, and closure the project.> Milestone

v<x.x>

<Construction Stage>

<The R2.0 Operational Capability Milestone marks the end of the Construction Stage. Release 2.0 software is ready for packaging.>

<Transition Stage>

<The R2.0 Release Milestone marks the end of the Transition Stage. At this point all capabilities, as defined in the SRS, are installed and available for the users.> Post mortem meeting

Termination Stage

3.2. Iteration objectives
<Define only risks and refer to Section 1.4 if a stage has only 1 iteration. Fill to table below only for these stages having more than 1 iteration> Table 9: Project iterations objectives
Stage <Definition Stage> Iteration <Preliminar y Iteration> Description <Defines business model, product requirements, project plan, and business case.> Associated Milestones <Business Case Review> Risks Addressed <Clarifies user requirements up front. Develops realistic project plans and scope. Determines feasibility of project from a business point of view.> <Solution Stage> <E1 Iteration – Develop Architectura l Prototype> <Completes analysis & design for all R1 use cases. Develops the architectural prototype for R1. Complete Analysis and Design for all high risk R2 use cases.> <Constructio <C1 <Implement and <R1 Beta> <Architectural Prototype> <Architectural issues clarified. Technical risks mitigated. Early prototype for user review.>

<All key features

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

11/21

<Project code>-Project Plan
Stage n Stage> Iteration Iteration – Develop R1 Beta> Description test R1 use cases to provide the R1 Beta Version.> Associated Milestones

v<x.x>
Risks Addressed from a user and architectural prospective implemented in the Beta. User feedback prior to release of R1.>

<C2 Iteration – Develop R1 Release>

<Implement and test remaining R1 use cases, fix defects from Beta, and incorporate feedback from Beta. Develops the R1 system.>

<R1 Software>

<R1 fully reviewed by user community. Product quality should be high. Defects minimized. Cost of quality reduced.>

<C3 Iteration – Develop R2 Release>

<Design, implement, and test R2 use cases. Incorporate enhancements and defects from R1. Develops the R2 system.>

<R2 Software>

<Quick release of R2 addresses customer satisfaction. All key functionality provided in System by R2 Release.>

<Transition Stage>

<T1 Iteration – R1 Release>

<Package, distribute, and install R1 Release.>

<R1 Released>

<Two stage release minimizes defects. Two stage release provides easier transition for users.>

<T2 Iteration – R2 Release>

<Package, distribute, and install R2 Release.>

<R2 Released>

<Two stage release minimizes defects. Two stage release provides easier transition for users.>

3.3. Project schedule
<Refor to initial MS Project plan of the project.>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

12/21

<Project code>-Project Plan

v<x.x>

4. PROCESS TAILORING/DEVIATION
The operational process for the project is based on the development process model defined in the FPT Software Process Handbook and Fsoft guidelines. <There are tailoring/deviations from the Standard Methodology> <Refer to Project Database if it’s not special request for filling in the table below> Table 10: Process tailoring/deviation
No. Tailoring/deviation Added/Modifie d/Deleted Reason for tailoring/deviation Tailoring or Deviation ?

<NA if it’s not available>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

13/21

<Project code>-Project Plan

v<x.x>

5. RESOURCE PLAN

5.1. Project Organization
5.1.1.Organizational structure <Describe the organization structure of the project team, including management and customer, if available. Figure below is an example of project organizational structure>

5.1.2.Project team Table 11: Project team
No. Name Position Start Date End Date Working time5

Management team 1 2 PM PTL

5

Fill here any note about working time as % of total effort or how many hours per day or per week.

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

14/21

<Project code>-Project Plan
No. Name Position Start Date End Date

v<x.x>
Working time

Management team <Name of team i> 3 <Identify code of these processes which the team has responsibility for> TL

5.2. External interfaces
5.2.1.FPT interfaces Table 12: FPT interfaces
No. Name <SEPG representative > <Infrastructur e name> <Add here if it’s needed> Position QA Responsibilities6 Process control and audit, support on process related issues Tel, Fax, Email

1

2

5.2.2.Customer’s interfaces Table13: Customer’s interfaces
No. Name <NA if it’s not available> Position Responsibilities7 Tel, Fax, Email

5.2.3.Subcontract Table14: Subcontract plan
No. Job <NA if it’s not available> Deliverable Delivery date Note

6 7

Including required deliverables and delivery time, if applicable Including required deliverables and delivery time, if applicable

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

15/21

<Project code>-Project Plan

v<x.x>

5.3. Project communication
5.3.1.Internal project communication <Describe internal project planning, monitoring, control and communication mechanism including task assign, reports, reviews, meetings> 5.3.2.Communication with management board of department <Describe monitoring, control and communication mechanism including reports, reviews, meetings with management board of department who manages this project> 5.3.3.Communication with customer <Describe monitoring, control and communication mechanism including reports, reviews, meetings with customer. Make strongly attention to changes management, customer feedback and complaints, issue handling> 5.3.4.Others <Describe monitoring, control and communication mechanism including reports, reviews, meetings with other bodies as FPT interfaces, subcontractors... NA if it’s not available>

5.4. Training plan
Table 15: Training plan
No. 1 Topic <NA if it’s not available> Description <Fill here the training objectives and contents, methodology (self training, class, seminar, CBT...), pass criteria and evaluation method.> Participant s Time <Fill here the training duration and planned complete date> Waiver criteria <Fill here the criteria of a project member to skip all or part of the training>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

16/21

<Project code>-Project Plan

v<x.x>

5.5. Tools and Infrastructure
5.5.1.Software <List all required software, in-house tools or tools to be developed in project> 5.5.2.Hardware <List all required hardware> 5.5.3.Others infrastructures <List all other required infrastructure resources viz. disk space, servers, environments>

5.6. Project Finance
5.6.1.Invoice schedule Table 16: Invoice schedule
No. Item Target date for Invoicing Amount % of total revenue Conditions are required to raise an invoice

<N/A if it’s not available>

5.6.2.Project cost Table 17: Project costing
Labor Activities <Refer to Project Database if it’s not special request for filling here> Total Effort: TOTAL LABOR: EFFORT (md) Cost

NonLabor

(attach supporting details) <N/A if it’s not special request> TOTAL

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

17/21

<Project code>-Project Plan
NONLABOR: TOTAL BUDGET:

v<x.x>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

18/21

<Project code>-Project Plan

v<x.x>

6. QUALITY MANAGEMENT

6.1. Quality objectives
<This section should reference the section of the Software Requirements Specification that deals with quality requirements. The organization quality objective/norm should also be highlighted here. If the organizational quality objective is tailored for this specific project, the rational for arriving at this quality objective should be addressed in the Notes section.> <Refer to Work Order and Project Database if it’s not special items for the project or special request for filling here> Table 18: Quality objectives
No Quality objectives Unit Norm Target Notes

6.2. Quality activities
<This section contains the Review, Audit and other quality activities. The Review and Audit activities specify the schedule, resources, and methods and procedures to be used in conducting project reviews and audits. The plan details the various types of reviews and audits to be carried out during the project, and identify any external agencies that are expected to approve or regulate the work products of the project.> 6.2.1.Strategy to achieve the quality objectives <List down all best practices and technicalities to be included as part of the design, testing etc, in order to achieve such performance criteria> 6.2.2.Review and inspection Table19: Reviews and inspection
No Items under Review/Inspection Conductor Date Approved by Note

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

19/21

<Project code>-Project Plan 6.2.3.Other activities

v<x.x>

Table20: Others quality activities
No. 1 2 3 Activity Metric collection Internal audits Quality objective tracking <Add here if needed> Date/ frequency Responsibility Note <Refer to guideline if needed>

6.2.4.Metrics Plan <Refer to Project Database if it’s not special request for filling metrics in below table>
Metric to be collected <Size> <Effort> <Defects> <Schedule> <Add here if needed> Unit of Measurement <LOC, FP, S/M/C count> <Person-days> <Number of Defects> <Elapsed time> Tools used if any

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

20/21

<Project code>-Project Plan

v<x.x>

7. CONFIGURATION MANAGEMENT
<Refer to the CM plan or insert here the contents of the CM plan as appropriated>

01e-BM/PM/HDCV/FSOFT v1/4

Internal use

21/21

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

Master Your Semester with a Special Offer from Scribd & The New York Times