1.
Organization Approval Gate Methodology Artifact Alignment Matrix
Gate 1 Gate 2 Gate 3 Gate 4 Gate 5
Frame When To Use Key Business rules Concept Post Implementation
Planning Execution Closure
work (Unique to each organization) (Unique to each organization) Initiation Review
Examples: Examples: Examples: Examples: Examples: Examples: Examples:
- New Product - At least 2 members of team familiar - Business Case - Determine # iterations - Execution of iterations - All Iterations retrospective - Finalize project costs
- New business process with 1 Agile Method - Project Portfolio Prioritization - Release Planning - Daily Scrum - Next Release Planning - Archive documentation
- - Agile team is co-located or has web - Approval - Daily Plan - Sprint change request - Outstanding Issues - Complete Project Closure
conferencing tools - Product Backlog of Features - Scope Initial iteration/sprint - Sprint Retrospective - Post Implementation Document
- Agile Team is cross functional (not - Release Planning - Requirements refinement Monitoring - Release project team to other
Agile just technology) - Architectural design - Paper prototyping - Hot fixes if required projects
- Product Vision and Preliminary - High level plan - Coding, Configuration - Executive Closure
Roadmap available - Scope statement - System & User Testing presentation
- Team is passionate and driven - Other business deliverables - Schedule ROI presentation
Examples: Examples: Examples: Examples: Examples: Examples: Examples:
- Maintenance existing product - Established architecture - Business Case - Finalize base line project plan - Coding - Lessons Learned - Finalize project costs
- Infrastructure Application - Known repeatable delivery process - Project Portfolio Prioritization - Create project risk plan - System Unit Testing - Post Implementation Review - Archive documentation
- - Fixed time fixed price contract - Approval - Detailed requirements - User Acceptance Testing - Outstanding issues and work - Complete Project Closure
- Performance metrics are focused on - Architectural design documentation - Interface testing arounds documented Document
delivery date and budget - High level plan - Requirements signoff - Operating Procedures - Hot fixes as required - Release project team to other
Waterfall - Project Charter - Interfaces high-level plan - Alpha testing - Post Implementation projects
- Marketing plan if applicable - Beta Testing Monitoring - Executive Closure
- Operational Readiness presentation
- Performance Testing - Schedule ROI presentation
- Security Testing
- Business Continuity Testing
Examples: Examples: Examples: Examples: Examples: Examples: Examples:
- Purchasing 3rd party solution - Preliminary Research has identified 1 - Business Case - Requirements for RFI/RFP - Installation - Lessons Learned - Finalize project costs
- Configuration & Customization or more COTS that meets 80%+ of - Project Portfolio Prioritization - RFI/RFP process - Configuration - Post Implementation Review - Archive documentation
- business needs - Approval - Final 3rd Party Selection - Data Migration - Outstanding issues and work - Complete Project Closure
- COTS product has an open API - Architectural design - Contract Negotiations - Custom Code arounds documented Document
(Application Protocol Interface) - Integration design - Software Hardware Purchase - Interface testing - Hot fixes as required - Release project team to other
COTS - Expertise for COTS - High level plan - Kickoff with 3rd party - User Acceptance Testing - Post Implementation projects
(Commercial Off integration/adaptation is available - Product Training - Operating Procedures Monitoring - Executive Closure
The Shelf)
within the organization or can be - Refinement of plan with 3rd - Operational Readiness - Future enhancement presentation
outsourced Party - Performance Testing requests - Schedule ROI presentation
- Data Transformation Mapping - Security Testing
- Final Data freeze and Migration
- Business Continuity Testing
Examples: Examples: Examples: Examples: Examples: Examples: Examples:
- Business Process Improvement - Target goals / metrics are not being - Business Case - Fact verification - Improve - Implement approved - Monitor Controls for 30 days - Finalize project costs
- System to System Process Review met - Project Portfolio Prioritization - Form project Team , recommendations - Refine controls - Archive documentation
- There are a lot of business work - Customer Satisfaction has decreased - Approval - Critical processes identified - Implement Controls - Monitor Controls for another - Complete Project Closure
arounds - Operational processes are unstable - High-level project timeline - Define& Measure Problem - Monitor Controls for 30 days 30 days Document
- There are a lot of special branches or inconsistent - Problem Statement - Future state process map - Identify other opportunities - Release project team to other
DMAIC to routine operational processes - It has been 2 years or greater since a - Project boundaries/Scope - Analyze for continuous improvement projects
business or systems process statement - Process Gap Analysis - Executive Closure
audit/review was completed - Project Charter - Improvement Recommendation presentation
- Current State Process & Approval - Schedule ROI presentation

2.
Organization Gated Methodology Alignment Timing Magnitude Matrix .
Gate 1 Gate 2 Gate 3 Gate 4 Gate 5
Frame Timing Notes: Concept
Planning Execution Post Implementation Review Closure
work (Unique to each organization) Initiation
Timing Notes: 3 weeks to 6 months 4 weeks to 6 weeks 3 months to 6 months 4 weeks to 6 weeks 4 weeks to 6 weeks
It will depend on how many releases you This will depend on data available This will depend on your teams This will depend on number of This will depend on the sprint timing This will depend on your close out
have a year and how many weeks you plan to for a business case and project familiarity with Agile/Scrum and any releases in a year, iteration and hot fixes that may need to be procedures for projects. Note
have per iteration. For example if there are intake & approval process timing outstanding information or frequency. implemented it is typically scheduling of the ROI presentation
Agile 3 releases a year, each release is 4 months within your organization. refinement of information from Gate recommended that 30 days be the will be dependent on business case.
and if each iteration is 2 weeks there would 1. E.g. 3 Annual Releases = 4 months minimum monitoring period. Typically scheduled for 1 month
be 6 to 8 iterations. after start of payback period.
4 months * 2 weeks = 8 Iterations
Timing Notes: 3 weeks to 6 months 6 weeks to 8 weeks 3 months to 18 months 4 weeks to 6 weeks 4 weeks to 6 weeks
There are several estimating techniques. This will depend on data available This will depend on the level of This will depend on the complexity This on the quality of the solution This will depend on your close out
One example would be function point for a business case and project ambiguity and amount of change of the changes and interface impacts deployed and it's ability to meet procedures for projects. Note
analysis and estimating. intake & approval process timing proposed to the existing platform. being introduced. In some business needs. Typically scheduling of the ROI presentation
within your organization. As well as the level of needs organizations projects need to recommended that 30 days to 45 will be dependent on business case.
Waterfall http://en.wikipedia.org/wiki/Function_point understanding by the business and complete within the fiscal year and if days be the minimum monitoring Typically scheduled for 1 month
the project team. the project exceeds 18 months will period. after start of payback period.
be artificially factored into 2 projects
or phases
Timing Notes: 3 weeks to 6 months 4 weeks to 6 weeks 8 weeks to 12 weeks 4 weeks to 6 weeks 4 weeks to 6 weeks
This is dependent on the 3rd parties This will depend on data available This will depend on the This will depend on the % of This on how well the COTS solution This will depend on your close out
standard implementation schedule being for a business case and project duration/timing of the RFI/RFP business needs the application could be integrated into your procedures for projects. Note
interweaved with your organizations intake & approval process timing process as well as the number of meets, as well as 3rd party ability to existing environment and the scheduling of the ROI presentation
COTS approval and control processes within your organization. qualified 3rd Party providers who implement solution, and the amount support level contractually will be dependent on business case.
(Commercial Off submit an RFI/RFP response. of customization that is required. negotiated typically recommended Typically scheduled for 1 month
The Shelf) that 30 days to 45 days be the after start of payback period.
minimum monitoring period.
Timing Notes: 3 weeks to 6 months 4 weeks to 6 weeks 3 months to 18 months 4 weeks to 9 weeks 4 weeks to 6 weeks
The overall estimation can be depended on This will depend on data available This will depend on information This will depend on the This on the recommendations This will depend on your close out
the improvements selected and may for a business case and project available, ability of team to define recommendations from implemented and the ability to procedures for projects. Note
leverage other accepted organizational intake & approval process timing this issues and collected improvement analysis and the implement sustainable scheduling of the ROI presentation
methodologies. within your organization. measurement data to prioritize the business drivers defining the need improvement. It is typically will be dependent on business case.
impacts. E.g. If there is no existing for process improvement. recommended to monitor Typically scheduled for 1 month
DMAIC
baseline data this will need to be improvement for 30 days, tweak after start of payback period.
collected first. improvements and controls and then
monitor for another 30 days