• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Status pmo report
 

Status pmo report

on

  • 725 views

 

Statistics

Views

Total Views
725
Views on SlideShare
725
Embed Views
0

Actions

Likes
0
Downloads
25
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Status pmo report Status pmo report Presentation Transcript

    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 PROJECT: <NAME> PROJECT MANAGER: <NAME> STATUS AS OF: <DATE> Status Summary Last Current Next Green, Yellow, Red is determined by the worst status from Issue/Risk Green in <module x> Blue in <module y> Issues – Critical and High Last Green - No Critical/High Issues Open Current Yellow - Critical/High Issue(s) = 1 to 15 Day Total Impact Next Red - Critical/High Issue(s) = 16+ Day Total Impact Indicate Total Impact Days for Critical/High Issues Issue ID Status Summary Description Summary Impact Action Plan Action Item Owner Due Date 1 Open QA/Testing Methodology and plan Standardize across the projects Create the documents <group> <date> 2 Open Finalize the project plan (estimated time). Dependant on Design phase completion Hinders the project management Get the Build dates from Pilat <group> <date> 3 Open Finalize Testing Plan Hinders the project management Additional QA resources required to complete testing <group> <date> 4 open Training Plan Hinders the project management Travel cost may be incurred. <group> <date> Page 1 of 6
    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 Risks – Critical and High Last Green - No Critical/High Issues Open Current Yellow - Critical/High Issue(s) = 1 to 15 Day Total Impact Next Red - Critical/High Issue(s) = 16+ Day Total Impact Indicate Total Potential Impact Days for Critical/High Risks Ris k ID Strategy Summary Description Summary Potential Impact Potential Impact (1-10) Probability (1-10) Risk Rating (Impact x Probability) Mitigation Plan Action Item Owner Due Date 1 Mitigation QA / Testing If we do not have a standard methodology and resources for QA/Testing assessment then there is no accountability and repeatability of the adhoc QA/test done on the vendor solution. 9 2 18 Develop or repurpose existing QA methodology. Get internal resources for QA/Testing who understands SNI’s business. <group> 2 Mitigation Business availability and commitment If there are delays in reviews, signoffs and postponements of meetings by the business then this will have a snowball effect on the build and the project timeline will get pushed out. 5 3 15 Business partners have to keep their commitments and availability to the project. <group> 3 Mitigation Vendor availability and commitment If adequate vendor resources are not provided or language barriers are not addressed then additional time and meetings will be necessary to bring closure to pertinent 9 3 27 Vendor has added additional resources and addressed the language concerns. Additional resources may still be needed to maintain the current timeline. <group> Page 2 of 6
    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 items. 4 Mitigation Infrastructure If all the environments are not ready the project timeline could slip. Order for the hardware & software already placed. <group> Page 3 of 6
    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 Project Phases Phase Description Baseline Start Date Forecast / Actual Start Date Baseline Finish Date Forecast / Actual Finish Date Risk / Issue ID(s) Comments / Reason for Delay Design issue id 1 Resource (SNI-IT, Pilat, SNI-Business) availability - Functional - Reports - Electronic (workflow) notifications - <App Name> Hands on Session with Business - <App Name> Workflows and Use case Documentation - <App Name> BRD Documentation - Integration Design - Conversion Design - Acceptance of the Design Phase Build - Functional Build Dependent on Design completion - Integration Build - Data Conversion Build - Acceptance of the Build Phase Testing TBD TBD QA lead working on the plan and estimation Training TBD TBD Dependent on Build and Testing completion - Understand the base <App Name> system and train the super users and train the trainer - Prepare the training documents - UAT Training Implementation TBD TBD Dependent on Training completion Closing Phase TBD TBD Dependent on Implementation completion Page 4 of 6
    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 Critical Tasks Completed of Overdue from Last Reporting Period # Detailed Tasks Project Phase Due Date Status Risk / Issue ID(s) Comments / Reason for Delay Critical Tasks to be Completed for Next Reporting Period # Detailed Tasks Project Phase Due Date Status Risk / Issue ID(s) Comments / Reason for Delay Action Items Pending Management Decision Issue / Risk ID Severity Due Date Action Item Owner Last Update Status Page 5 of 6
    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 Appendix 1 Key Accomplishments and status for last week • Ongoing work on: o <x> Design specifications o <y> Interfaces. • Signed Design documents so far: o So far <x> of <y> Design specifications signed. o So far <x> of <y> Interface specifications signed. • Ongoing work on Workflow process and Use case documentations • Ongoing work on Reports. 2 Items to Watch this week • Reviews of the ongoing <x> Design specifications. • Reviews of the ongoing <x> Interfaces. • Ongoing work on Workflow process and Use case documentation • Ongoing work on Reports 3 Key Issues (for resolution) • Blah blah • Blah blah OTHER ISSUES??? Next Session <Date> Page 6 of 6
    • <<COMPANYCOMPANY NAMENAME>> PPROJECTROJECT SSTATUSTATUS RREPORTEPORT 11 Appendix 1 Key Accomplishments and status for last week • Ongoing work on: o <x> Design specifications o <y> Interfaces. • Signed Design documents so far: o So far <x> of <y> Design specifications signed. o So far <x> of <y> Interface specifications signed. • Ongoing work on Workflow process and Use case documentations • Ongoing work on Reports. 2 Items to Watch this week • Reviews of the ongoing <x> Design specifications. • Reviews of the ongoing <x> Interfaces. • Ongoing work on Workflow process and Use case documentation • Ongoing work on Reports 3 Key Issues (for resolution) • Blah blah • Blah blah OTHER ISSUES??? Next Session <Date> Page 6 of 6