|
英国留学生项目管理作业写作需求样板：Effort Collection System
Project Charter
Version 1.0
Prepared by: Ted Gradell
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
REVISION HISTORY
VERSION DATE AUTHOR(S) REVISION NOTES
0.1 5-03-04 Ted Gradell Draft version 0.1 for Software Project
Management
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
TABLE OF CONTENTS
PROJECT OVERVIEW ...............................................................................................................1
PROJECT OBJECTIVES.............................................................................................................1
PROJECT SCOPE.........................................................................................................................1
IN SCOPE:.....................................................................................................................................1
OUT OF SCOPE:.............................................................................................................................2
DELIVERABLES PRODUCED: ...........................................................................................................2
ORGANIZATIONS/STAKEHOLDERS AFFECTED OR IMPACTED.................................2
PROJECT ESTIMATED EFFORT / COST / DURATION......................................................2
ESTIMATED COST: .........................................................................................................................2
ESTIMATED EFFORT:......................................................................................................................2
PROJECT MILESTONES: ..................................................................................................................3
PROJECT ASSUMPTIONS.........................................................................................................3
PROJECT RISKS..........................................................................................................................3
PROJECT APPROACH .................................................................................................................
MANAGEMENT APPROACH...............................................................................................................
Scope Change Management.....................................................................................................
Issue Management....................................................................................................................
TECHNICAL APPROACH....................................................................................................................
Activity 1: Environment Setup (Development, Training, Pre-Production, Production)..........#p#分页标题#e#
PROJECT ORGANIZATION........................................................................................................
PROJECT APPROVALS..............................................................................................................5
APPENDICES...............................................................................................................................6
APPENDIX A: PROJECT SCHEDULE .................................................................................................7
APPENDIX B: PROJECT BUDGET.....................................................................................................9
APPENDIX C: PROJECT STATUS REPORT TEMPLATE......................................................................11
APPENDIX D: SCOPE CHANGE REQUEST TEMPLATE ......................................................................12
APPENDIX E: ISSUE LOG TEMPLATE .............................................................................................13
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
Project Statement
Develop and deploy an enterprise effort collection system for National Laboratory, replacing the
32 currently in place. The new Effort Collection System will support the Oracle Projects
implementation project and will be deployed concurrently.
The new ECS system will be completed by January 2005 and will not exceed 6000 hours of FTE.
Project Objectives
The ECS will meet the following objectives in support of NL project management.
• Install and configure the hardware and operating system software for development,
training, pre-production and production environments
• Develop and deploy and enterprise application for the collection of effort from all types
and levels of employees.
• Integrate with Oracle Application to account for effort by Project and Work Break Down
Structure.
• Document application, integration and architecture as required to support ECS
Project Scope
The purpose of this project is to provide the hardware and software environment necessary for
the development, implementation of ECS and to provide a seamless integration to Oracle Project
Management modules. Do you have control over all elements contributing to seamless
integration?
In Scope:
• Hardware and operating system software installation/configuration to support the
following environments:
• Development (Dev) – code development
• Training (Trn) – training for the prototype user community
• Pre Production (Pre) – quality assurance and load testing
• Production (Prd) – controlled production for use by the prototype users
• ECS application designed and developed in an J2E architecture
• Development – of effort collection application with the following:#p#分页标题#e#
o Validation of employee, project and account
o Query and report generation as defined in requirements
o Capture of effort hours
• Integration to Oracle Project Management modules
• Database and mid-tier integration
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
Out of Scope:
• Installation of Oracle Project Management Modules
• Application tuning resulting from load testing
• Portal Integration
Deliverables:
• Project Definition to describe the project objectives, scope, effort/cost/duration,
assumptions, risks, approach and organization
• Detailed Project Work Plan to identify all milestones, activities and tasks, resources,
durations and deliverables.
• Hardware setup for Development, Training, Pre-Production, and Production suitable for
use by the ECS development team
• Web based application deployed through NL portal
• Database and mid-tier (application server) tuning approach and results
• Work Products including documented plans, work flows and checklists for the hardware
setup and configuration process, the software installation and configuration process, the
software cloning process
Organizations/Stakeholders Affected or Impacted
The impact of this project on other organizations needs to be determined to ensure that the right
people and functional areas are involved and communication is directed appropriately.
STAKEHOLDERS
Who are the targets of the
project? (Customers,
Beneficiaries)
INVOLVEMENT
How involved are the
stakeholders?
(High/Medium/Low)
EXPECTED OUTCOME
Will the stakeholder Gain,
Lose, or Break Even?
CRITICALITY TO
SUCCESS
(High/Medium/Low)
LIKELY STANCE
(Supportive,
Uncommitted, Not
Supportive)
NL Projects
Mgt
High Gain High Supportive
NL CFO High Gain High Supportive
NL Project Staff High Break Even High Uncommitted
Table 1: Affected Stakeholders
Project Estimated Effort / Cost / Duration
Estimated Cost:
The Information Technology effort cost is estimated to be $600,000 and will be completed by
May 1, 2005. The estimated effort cost was derived as follows:
• Daily resource rates were applied in MicroSoft Project Schedule (Appendix A) to obtain
task costs shown in the Project Budget worksheet (Appendix B)
• Task costs were spread by month in the Project Budget worksheet (Appendix B)
Estimated Effort:
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
The ITS effort is estimated to be 6000 hours FTE for the project and was calculated as total
budget cost per month / average effort cost (Appendix B)
Project Milestones:#p#分页标题#e#
The table on the following page identifies the key milestone tasks and dates with the associated
deliverables. The Project Schedule included in Appendix A and the Project Budget included in
Appendix B support the table.
MILESTONE
MILESTONE
DATE DELIVERABLE(S)
Project Planning 6-01-04 • Project Definition
Functional Requirements 9-01-04 • Functional requirements from key
users
Environment
Hardware Setup 10-07-04 • Development and Test Hardware
12-01-04 • Production
Application Development
Deployment Phase identification 10-01-04 • Release schedule
Release 1 12-01-04 • Application to Test
Release 2 02-01-05 • Application to Test
Application Deployment
Release 1 02-15-05 • Release 1 to productions
Release 2 05-01-05 • Release 2 to production
Table 2: Project Milestones
Project Assumptions
A project assumption is defined as an event with a low probability of occurring (a low level risk)
but having significant implications if the event does in fact occur. An assumption is
characterized as being outside the control of the project team. Based on the current knowledge
today, the project assumptions are listed below. If an assumption is invalidated at a later date,
then the activities and estimates in the project plan will be re-evaluated and adjusted accordingly
• Resources are available with proper skill set
• Oracle Project Modules will be implemented as scheduled
Project Risks
Project risks are characteristics, circumstances or features of the project environment, having a
high probability of occurring, that may have an adverse effect on the project or the quality of its
deliverables. Known risks identified with this project have been included below.
RISK AREA
LEVEL
(H/M/L) RISK PLAN
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
Resources H Utilize external consulting
Oracle Project Modules not
implemented
H Develop ECS and deploy when ready
Table 3: Project Risks
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
Project Approvals
_________________________________________ ___________________
Ted Gradell Date
AIS IT Manager (CFO)
_________________________________________ ___________________
XYZ Date
Project Manager
_________________________________________ ___________________
ABC Date
CPMW ITS Sub Project Manager
_________________________________________ ___________________
CPU DOWN Date
Information Technology Services Manager
Project Charter
Project Charter for Software Project Management Last Date Revised: 05-04-04
Appendices
The following Appendices contain Project Management documents as follows:#p#分页标题#e#
Appendix A: Project Schedule
Appendix B: Project Budget
Appendix C: Project Status Report Template
Appendix D: Scope Change Request Template
Appendix E: Issue Log Template
Project Charter for Software Project Management Last Date Revised: 05-04-04
Appendix A: Project Schedule
The Project Schedule on the following page identifies the activities, tasks, duration, estimated
costs, start and finish dates and resources at a high level for this project effort. This project
schedule supports the schedule identified in Table 2: Project Milestones.
Project Charter for Software Project Management Last Date Revised: 05-04-04
Project Charter for Software Project Management Last Date Revised: 05-04-04
Appendix B: Project Budget
The Project Budget worksheet on the following page identifies the activities, tasks, duration, start
and finish dates, resources, and estimated task costs from the Project Schedule in Appendix A.
The task costs are spread across the months in the fiscal year based upon the task start and finish
dates.
Assumptions Used:
• 152.1 hours per month
• ITS Management Factor (normally 5%) not applied
• A 10% Contingency Factor was applied
• Resource standard salary rates obtained from the Resource Manager
• Resource rates include OPC
• Resource rates include effort factor of 85% for all five resources
• Tasks performed by 4 resources used a 50% factor on the duration to allow for cross
training (applied on the Project Schedule)
• Costs for the month of September are not included in the task totals (far right column)
Process Used:
• Daily resource rates were applied in MicroSoft Project Schedule to obtain task costs
• Task costs were spread by month in the Project Budget worksheet
• FTE per month calculated as total budget cost per month / average effort cost
• Average effort cost calculated as actual monthly rate for the 5 resources / 5
Project Definition
charter_example_a.doc Page 10 Last Date Revised: 11/21/2003
Project Definition
charter_example_a.doc Page 11 Last Date Revised: 11/21/2003
Appendix C: Project Status Report Template
Tasks Completed This Period Week Ending 4-30-04
Task Description #1 – COMPLETE
Brief description of completed tasks (Team Member Name)
Task Description #2 – xx% Complete
• Brief description of completed tasks (Team Member Name)
Tasks Expected to be Completed Next Period
Task Description #1 – xx% Complete
• Brief description of tasks expected to be completed (Team Member Name)
Issues
• Issue #1 – Date Reported, Assigned To, Resolution, Escalated To, Date Resolved#p#分页标题#e#
-OR-
• Include Issue Log
Change Requests
• Change Request #xx – Status (received, accepted), Impact
Comments
charter_example_a.doc Page 12 Last Date Revised: 11/21/2003
Appendix D: Scope Change Request Template
Change Request Nbr: Requested By: Date Requested:
Description:
Business Benefit:
Implications of Not Making the Change:
Impact Analysis to the Project:
Alternatives:
Final Resolution:
Project Manager Approval:
Sponsor Approval:
Project Definition
charter_example_a.doc Page 13 Last Date Revised: 11/21/2003
指导英国留学生作业Appendix E: Issue Log Template
Issue
# Issue Description and Impact to Project
Priority
(M/H/L)
Date
Reported Reported By Assigned To
Date
Resolved Status Resolution/Comments
1 .
2
3
|
