2.1.0 Start PES Documents
Start PES Meeting
Presented By:
Date:
Why New Systems Fail: An Insider's Guide to Successful IT Projects
A. ERP: The Implementation Cycle (Computer Weekly Professional)
Customer Name: - - - - - - - - - - - - - - - -
Location: - - - - - - - - - - - - - - - -
Customer Profile: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Project Manager: - - - - - - - - - - - - - - - - - -
Presented By: - - - - - - - - - - - - - - - - - -
Review Period: - - - - - - - - - - - - - - - - - -
B. Overview
Total Effort M. Months: - - - - - - -
Start Date: - - - - - - - - -
Planned End Date : - - - - - - - - -
Projected End Date: - - - - - - - - -
Project Description
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Project Status Summary
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C. Technical Project Platform
Hardware
System Software
Application Software
D. Project Methodology
1. Requirements / Scope / Determination of Project Size
2. Effort Estimation
3. Tracking and Measurements of work done, costs and schedule
4. Testing, Deliverables, Release
5. Acceptance and Completion Criteria
6. Escalation, Progress Reports etc.
7. Change Control / Contract Management / Claim Management
8. Resources - Manpower, Training, Infrastructure etc.
E. Project Organization Staffing
1. Project Organization Structure
2. Project Staffing
F. Project Schedule Status Summary
Start PES Meeting
Date:
Why New Systems Fail: An Insider's Guide to Successful IT Projects
A.
Location: - - - - - - - - - - - - - - - -
Customer Profile: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Project Manager: - - - - - - - - - - - - - - - - - -
Presented By: - - - - - - - - - - - - - - - - - -
Review Period: - - - - - - - - - - - - - - - - - -
B. Overview
Total Effort M. Months: - - - - - - -
Start Date: - - - - - - - - -
Planned End Date : - - - - - - - - -
Projected End Date: - - - - - - - - -
Project Description
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Project Status Summary
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C. Technical Project Platform
Hardware
System Software
Application Software
D. Project Methodology
1. Requirements / Scope / Determination of Project Size
2. Effort Estimation
3. Tracking and Measurements of work done, costs and schedule
4. Testing, Deliverables, Release
5. Acceptance and Completion Criteria
6. Escalation, Progress Reports etc.
7. Change Control / Contract Management / Claim Management
8. Resources - Manpower, Training, Infrastructure etc.
E. Project Organization Staffing
1. Project Organization Structure
2. Project Staffing
Short Name | Role | Name |
SBU Head | SBU Head | |
SM | Systems Manager | |
AM | Account Manager | |
QM | Quality Manager | |
FC | Financial Controller | |
PM | Project Manager | |
PQM | Project Quality Manger | |
OC | On-Site Co-ordinator | |
TC | Technical Controller | |
TL | Team Lead | |
PT | Project Team Member |
F. Project Schedule Status Summary
Project Risks | ||
No. | R I S K | Mitigation Plans |
1 | ||
2 |
G. Project Goals
H. Project Standards
Defect Prevention Activities
Customer Issues
• Customer Perception
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Customer Feedback
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Our Concerns
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
No comments:
Post a Comment