Program Mgmt Framework
Download as PPTX, PDF2 likes444 views
This document outlines the framework for managing projects, including stages from intake to deployment and closeout. It defines entry and exit criteria for key stages: plan and design, build and configure, QA test, UAT, deployment, and warranty/close. Process details include resource allocation timelines, documentation requirements, and risk management procedures from program initiation through production release and transition to support. The framework is intended to standardize project delivery and provide structure, oversight, and governance for consistent management of initiatives from start to finish.
Program Mgmt Framework
- 2. Intake Process Summary 2 Committed Pipeline Booked Slated Horizon 2 Horizon 3 Project Baseline Yes No No No Resources Allocated Yes Yes No No In Resource Tool Yes Yes Yes Maybe Effort Final Final OOM +/- 100% Estimate Documentation Signed SOW SOW issued Assumptions None Timelines In-flight to < 5 weeks < 8 weeks < 12 weeks < 6 months Probability 100% 90% 75% 50% Included in FinancialPlan Yes Yes Yes Place hold amount not to exceed forecast resource capacity Resource/Revenue Planning Responsibility Bruce Amson Bruce Amson Bruce Amson/ Raegan Stuart Raegan Stuart Data Management Torbjorn Zetterlund Torbjorn Zetterlund Rupali Das Raegan Stuart Included in project dashboard Yes Yes No No Product Development On Shelf Near completion/ On Shelf Requirements Complete Road mapped
- 3. Intake Process Summary 3 H3 “Horizon 3” ≤ 6 months or ≥ 50% Probability H2 “Horizon 2” ≤ 12 weeks or ≥ 75% Probability Resource Assignment Gate ≤ 12 weeks or ≥ 75% Probability Business Case & Prioritization PipelineCommitted Proceed No Slated ≤ 8 weeks SOW Issued Booked ≤ 5 weeks SOW Signed Project Start 0 weeks
- 4. Project– Plan and Design - Entry/Exit Criteria • Slide content Entry Criteria Exit Criteria •Project Charter / Project Management Plan •BRD Document •Business Requirements •Solution Architecture Design Doc •DR Requirements •Operational Gap Requirements •Draft Functional Specifications •Draft MS Project Schedule •Signed Off BRD •Functional Requirements •Non-Functional Requirements •Configuration Requirements •Signed Off Test Strategy •Infrastructure Plan •End User Acceptance Criteria •Baselined MS Project Schedule / Project Plan •Detailed Cost Estimation •Finalized Resource Plan •Finalized WBS •Training Plan
- 5. Project– Build and Configure - Entry/Exit Criteria • Slide content Entry Criteria Exit Criteria •Signed Off BRD •Functional Requirements •Non-Functional Requirements •Configuration Requirements •Signed Off Test Strategy •Infrastructure Plan •End User Acceptance Criteria •Baselined MS Project Schedule / Project Plan •Detailed Cost Estimation •Finalized Resource Plan •Finalized WBS •Training Plan •Completed Code/Configurations •Code Sign Off •Unit Test Cases Sign Off •Technical Design Documents •QC/SIT Test Plan Sign Off •QC/SIT Test Cases Reviewed •QC/SIT Test Scenarios and Requirements •UAT Test Plan •Implementation/Deployment Plan •Deployment Change request(DCR) •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate
- 6. Project Framework– QA Test - Entry/Exit Criteria • Slide content Entry Criteria Exit Criteria •Completed Code/Configurations •Code Sign Off •Unit Test Cases Sign Off •Technical Design Documents •QC/SIT Test Plan Sign Off •QC/SIT Test Cases Reviewed •QC/SIT Test Scenarios and Requirements •UAT Test Plan •Implementation/Deployment Plan •Deployment Change request(DCR) •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate •QC Test Results Summary •Software Integration Test Results Summary •QC Performance Test Results Summary •Bug Reviews/Triage Meetings •QC Release Regression Testing •QC Signoff • Deployment Change Request (DCR) to UAT • Deployment to UAT environment •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate
- 7. Project Framework– UAT - Entry/Exit Criteria • Slide content Entry Criteria Exit Criteria •QC Test Results Summary •Software Integration Test Results Summary •QC Performance Test Results Summary •Bug Reviews/Triage Meetings •QC Release Regression Testing •QC Signoff • Deployment Change Request (DCR) to UAT • Deployment to UAT environment •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate •UAT Test Result Summary •Bug Review/Triage Meetings •UAT Signoff •Signed Implementation Plan •Code Freeze Date •Training Artifact Signoff •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate
- 8. Project Framework– Deployment - Entry/Exit Criteria • Slide content Entry Criteria Exit Criteria •UAT Test Result Summary •Bug Review/Triage Meetings •UAT Signoff •Signed Implementation Plan •Code Freeze Date •Training Artifact Signoff •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate •RFC Approvals •Master Release Document (MRD) •Dry Run Signoff •Rollback signoff •RM After Action Report •Final Product Release to Production •BAT (Business Acceptance Testing) Signoff •Finalized Transition to Support Plan and activity •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate
- 9. Project Management Framework– Warranty and Close - Entry/Exit Criteria • Slide content Entry Criteria Exit Criteria •RFC Approvals •Master Release Document (MRD) •Dry Run Signoff •Rollback signoff •RM After Action Report •Final Product Release to Production •BAT (Business Acceptance Testing) Signoff •Finalized Transition to Support Plan and activity •Revised BRD, revised Functional specifications, revised Test Plans and Cases, revised PMP, and revised MS Project Schedule, as appropriate •Transition to Support •Closure Report •Lessons Learned •Completed Project Surveys •Official disbandment of Project Team •Closing resource ticket •All Project documentation submitted to Document Repository (SharePoint)
- 10. Project Framework - Risk Management • Program Level Risk Management Risk Identification and Mitigation/Contingency Planning Who Program Manager/Customer/TM/BM When Program Planning/Monthly /Event Driven/LAM (look ahead meetings) Inputs Risks identified during Proposal/Contract Phase, Issues List and Review Meetings Output Risk Management and Tracking Sheet (Risks identified, Risk Analysis, Risk Owner)