Project Status Report Template
Project Overview
Project Name: Project Objective: Report Version: Reporting Period: Project Overall Status: On schedule and no unmanageable risks On schedule with manageable risks Not on schedule with risks and issues Prepared By: Distributed To: John Doe – Business Analyst Xx – Sponsor Xx – VP Xx – Program Manager Xx – Project Manager 1.0 April xx, 2011 – April xx, 2011 (Weekly)
Monday, October 17, 2011
1
Executive Summary
Accomplishments
Completed during April xx, 2011:
Acc .1 Acc. 2 Acc. 3 Acc. 4
Functionality Progress
Upcoming for the week of April xx, 2011
Acc. 1 Acc. 2 Acc. 3 Acc. 4
Risk and Issues
Risk.1 Risk 2 Risk 3
Monday, October 17, 2011
2
Assumptions, Dependencies & Constraints
Item
EXAMPLE – Client XX will have their PCs upgraded before implementation of the report to the recommended config
Category
Assumption
Action
If the required config is not available it will seriously hinder the performance of the project and loose the end user confidence and buying power to the implementation Xx Xx
Assumption / Dependencies / Constraints
Monday, October 17, 2011
3
Change Management Status
CR Item
EXAMPLE – Additional 3 fields on the report
Date Identified
Reason for the Change
Missed in the initial requirement
Impact
Report needs to be redesigned and will take about 3 hours. Critical to have these fields and low impact to the schedule
Status
Approved by the Change Control Board Enhanced Report template is under review with the end users
Monday, October 17, 2011
4
Risk and Issues
Risk / Issue Item
EXAMPLE - No Business Analyst for the project
Category
Resource
Mitigation Plan
Use Jane Doe till a replacement is found Recruit a new business analyst
Action
Jane Doe is ramping up on the project details and a KT is already in place Xx xx
Schedule / Resource / Budget / Other
Monday, October 17, 2011
5
Requirement Progress
Requirement Category
Functional
Project Name: Project Objective: Report Version: Reporting Period: Project Overall Status: On schedule and no unmanageable risks On schedule with manageable risks Not on schedule with risks and issues Prepared By: Distributed To: John Doe – Business Analyst Xx – Sponsor Xx – VP Xx – Program Manager Xx – Project Manager 1.0 April xx, 2011 – April xx, 2011 (Weekly)
Monday, October 17, 2011
1
Executive Summary
Accomplishments
Completed during April xx, 2011:
Acc .1 Acc. 2 Acc. 3 Acc. 4
Functionality Progress
Upcoming for the week of April xx, 2011
Acc. 1 Acc. 2 Acc. 3 Acc. 4
Risk and Issues
Risk.1 Risk 2 Risk 3
Monday, October 17, 2011
2
Assumptions, Dependencies & Constraints
Item
EXAMPLE – Client XX will have their PCs upgraded before implementation of the report to the recommended config
Category
Assumption
Action
If the required config is not available it will seriously hinder the performance of the project and loose the end user confidence and buying power to the implementation Xx Xx
Assumption / Dependencies / Constraints
Monday, October 17, 2011
3
Change Management Status
CR Item
EXAMPLE – Additional 3 fields on the report
Date Identified
Reason for the Change
Missed in the initial requirement
Impact
Report needs to be redesigned and will take about 3 hours. Critical to have these fields and low impact to the schedule
Status
Approved by the Change Control Board Enhanced Report template is under review with the end users
Monday, October 17, 2011
4
Risk and Issues
Risk / Issue Item
EXAMPLE - No Business Analyst for the project
Category
Resource
Mitigation Plan
Use Jane Doe till a replacement is found Recruit a new business analyst
Action
Jane Doe is ramping up on the project details and a KT is already in place Xx xx
Schedule / Resource / Budget / Other
Monday, October 17, 2011
5
Requirement Progress
Requirement Category
Functional