Q-Gate Assessment Document

5/12/2018 Q-Gate Assessment Document - slidepdf.com

http://slidepdf.com/reader/full/q-gate-assessment-document 1/16

WBS / Title

Prior to using the Q-Gate assesment sheets make sure to add / remove / modify the key deliverab

individual project WBS and key deliverables. This should be done during the Phase Startup proce

phase.

During the actual Q-Gate assessment process go over each deliverable and assess whether it is a

exceptions (note the exceptions in the Comments field) or not accepted (note the action plan to pr

deliverable in the Comments field). Then based on the assessment assign (1) Green, (2) Yellow o

The impact rating numbers (column D) are provided to help you gauge importance of each deliver

(very high impact on project schedule, cost or risk). You may modify them based on individual proj

project may assign specific deliverables its own impact rating in comparison with other deliverable

impact rating is designed to indicate level of impact for each deliverable in relation to other deliver

figure derived from mathematical formula, but rather a reflection of importance of each deliverable

completing the deliverable at the time of Q-Gate.

WBS number of the deliverable in the ASAP Implementation Roadma

or key activity.

Q-Gate Instructions



Consider the following questions when identifying risks in a

Q-Gate is a tool to help the team reduce risk on a project. A Q-Gate can be Red, Yelllow or Green. It is Gre

completed to the satisfaction of the client and team. A Q-Gate is Yellow when even though an item has not project. A Yellow Q-Gate designates higer Risk. A Red Q-Gate get the color red, when one or more items h

client. SAP does not recommend moving forward with the project 'till all items are green. Please make sure

Gate and how, project run the elevated risks if all items are not green. Please do not limit yourself to these

You may have a lifecycle that is different than these. Be sure to list the PM Process for the lesson you are

Project Management Process

Initiating PhaseHow well was the project vision understood by team members?

Was the Project Sponsor involved as early as they needed to be?

Was there sufficient upper management support for the project to continue?

Were success criteria determined and understood?

Planning PhaseWas the project schedule useful and accurate?

Were contractors and other vendors brought in early/late, just in time?

Did the project team adhere to the schedule?

Was the skill set of the team members sufficient?

Q-Gate Leading Questions



W B S

1 Project PreparationProject Management

1.1.1 Phase Startup1.1.1.1 Phase Resources Allocation

1.1.1.2 Detailed Phase Schedule

1.1.1.3 Phase Kickoff Meeting

1.1.1.4 Handoff Checklist from Pre-project activities

1.1.2 Project Initiation

1.2.1 Project Strategic Framework

1 1 2 1 Business Case

T i t l e



1.1.4.5 Risk Register

1.1.4.6 Deliverable Acceptance Documents

1.1.4.7 Team Member Evaluations/Appraisals

1.1.4.8 Communications Matrix (updated)

1.1.4.9 Status Reports

1.1.4.10 Contractual Changes

1.1.5 Phase Sign-Off

1.1.5.1 Closed Contracts

1.1.5.2 Lessons Learned Log

1.1.5.3 Phase Completion Check (internal)

1.1.5.5 Phase Sign-Off DocumentOrganization Change Management

1.5.1 Change Charter

1.5.2 Initial Stakeholder Mapping and Business Readiness Assessment

1.5.3.1 Sponsorship Strategy

1.5.3.2 OCM Organization and Change Agent Network

1.5.4.1 Communication Plan

1.5.4.2 Initial Announcement

1.5.5.1 Organizational Alignment Strategy

1.5.5.2 Social Contract

1.5.6 Project Team Change Management

Training1.8.1.1 Project Team Training Plan

1.8.1.2 Trained Project Team (Level 1, Methodology and Organization Change Managem

1.8.2 Preliminary End-User Training and Documentation Strategy

Business Process Requirements, Design, Configuration and Testing

1.4.1 Business Scenario and Process Inventory

Lifecycle Data Management



W B S

2 Business BlueprintProject Management

2.1.1 Phase Startup

2.1.1.1 Phase Resources Allocation

2.1.1.2 Detailed Phase Schedule2.1.1.3 Phase Kickoff Meeting

2.1.2 E/M/C Results

2.1.2.2 Requests for Change

2.1.2.3 Change Log

2.1.2.4 Issue Log


T i t l e

Q

2 3 2 E d U T i i d D t ti St t



2.3.2 End-User Training and Documentation Strategy

Technical Solution Management

2.8.1 Authorization Requirements and Design

2.8.2 System Authentication Concept

2.10.1 Technical and Integration Design

2.10.2 Development Environment

2.10.3 System Administration Procedures

2.10.4 Support Procedures

2.10.5 Project IMG

Business Process Requirements, Design, Configuration and Testing

2.4.1 Business Organizational Structure2.4.2 General Settings & Master Data

2.4.3.1 Business Scenario Workshop Schedules

2.4.3.2 Business Scenario Overview

2.6.1.1 Business Process Workshop Schedules

2.6.1.2 Scenario #1

2.4.3.4.1 Scenario Requirements

2.6.1.2.1 Process #1

2.6.1.2.1.1 Business Process Requirements Documents

2.6.1.2.1.2 Business Process Models

2.6.1.2.1.3 Development Requirements

2.6.1.2.1.3.1 Forms Requirements2.6.1.2.1.3.2 Reporting Requirements

2.6.1.2.1.3.3 Interface Requirements

2.6.1.2.1.3.4 Enhancement Requirements

2.6.1.2.1.3.5 Workflow Requirements

2.6.1.2.1.3.6 Miscellaneous Development Requirements

2.6.1.2.2 Process #2 (to n)



W B S

3 RealizationProgram, Project, Risk and Quality Management

3.1.1 Phase Startup




3.1.2 E/M/C Results


3.1.2.3 Change Log

3 1 2 4 Issue Log

T i t l e



W B S


3.1.2 E/M/C Results

3.1.2.2 Requests for Change3.1.2.3 Change Log

3.1.2.4 Issue Log


3.1.2.6 Deliverable Acceptance documents



T i t l e

3 12 2 5 1 6 2 3 Test Results of Reports



3.12.2.5.1.6.2.3 Test Results of Reports

3.12.2.5.1.6.2.4 Documented Reports De

3.12.2.5.1.6.3 Interface Program (n)

3.12.2.5.1.6.3.1 Technical Specifications

3.12.2.5.1.6.3.2 Created Interfaces

3.12.2.5.1.6.3.3 Test Results of Interfaces

3.12.2.5.1.6.3.4 Documented Interfaces D

3.12.2.5.1.6.4 Enhancement Program (n)

3.12.2.5.1.6.4.1 Technical Specifications

3.12.2.5.1.6.4.2 Created Enhancements

3.12.2.5.1.6.4.3 Test Results of Enhance3.12.2.5.1.6.4.4 Documented Enhanceme

3.12.2.5.1.6.5 Workflow (n)

3.12.2.5.1.6.5.1 Specifications for Workflo

3.12.2.5.1.6.5.2 Developed Workflows

3.12.2.5.1.6.5.3 Test Results of Workflow

3.12.2.5.1.6.5.4 Documented Workflows

3.12.2.5.1.6.6 Miscellaneous Development (n)

3.12.2.5.1.6.6.1 Specifications for Miscell

3.12.2.5.1.6.6.2 Created Miscellaneous D

3.12.2.5.1.6.6.3 Test Results of Miscellan3.12.2.5.1.6.6.4 Documented Miscellaneo

3.12.2.5.2 Process #2 (to n)

3.12.2.6 Configured and Tested Scenario #2 (to n)

3.12.2.8 Migrated Configuration and Development to QA for Cycle n

3.12.2.9 Cycle Test Results/Updated Configuration Test Cases for Cycle n

3.12.2.10 Confirmation of Configuration and Development for Cycle n

3 12 3 R li ti f th E t i D t W h



W B S


3.1.2 E/M/C Results

3.1.2.2 Requests for Change3.1.2.3 Change Log

3.1.2.4 Issue Log


3.1.2.6 Deliverable Acceptance documents



T i t l e

3 14 2 1 Integration Test Results - Cycle 1



3.14.2.1 Integration Test Results - Cycle 1

3.14.2.1.1 Tested Scenario #1

3.14.2.1.2 Tested Scenario n

3.14.2.2 Functional User Acceptance Test Results - Cycle 2

3.14.2.2.1 User Acceptance of Scenario #1

3.14.2.2.2 User Acceptance of Scenario n

3.14.2.3 Preliminary Portal Performance Test Report

3.14.2.4 Portal User Acceptance Report

3.14.2.5 Resolved Integration Test Issues

3.14.2.6 Final Integration Test Sign-Off

Technical Solution Management3.9.1.1 Preliminary Production Support Pla

3.11.1 System User Roles and Authorizations

3.11.2 System Authentication

3.16.1 Production Infrastructure Ready

3.16.1.1 Data Center Ready for Production

3.16.1.2 Updated IT Infrastructure Document

3.16.2 Production Environment Design & Setup

3.17.1 Preparation for Performance Test

3.17.2 Performance-Test Plan

3.17.3 Test Environment and Test Scripts

3.17.4 System Test Plans

3.17.4.1 Failure Test Plan

3.17.4.2 System Administration Test Plan

3.17.4.3 Printing and Faxing Test Pla

3.17.4.4 Disaster Recovery Test Plan

3.17.4.5 Regression Test Plan

3 17 4 6 Backup-and-Restore Test Plan



W B S

4 Final PreparationProgram, Project, Risk and Quality Management

4.1.1 Phase Startup




4.1.2 E/M /C Results


4.1.2.3 Change Log

4.1.2.4 Issue Log


T i t l e

4 8 2 Production Cutover Sign-Off



4.8.2 Production Cutover Sign OffTechnical Solution Management

4.5.1 Established Functional and Technical Production Support

4.5.1.1 User Support Implemented

4.5.1.2 Solution Management Procedures

4.5.1.3 Monitoring Procedures

4.5.1.4 Systems and Application Handover to Support Organization

4.5.1.5 Complete IT Infrastructure Document

4.5.1.6 Change Management Document for Production

4.5.1.7 Refined Production Support Plan

4.5.1.8 Established Help Desk Organization

4.5.1.9 Reorganized Production Support Team

4.5.1.10 Long-Term Support Strategy

4.5.2 Approved Performance Tests

4.5.3 Approved System Tests

4.5.3.1 Failure Test Results

4.5.3.2 System Administration Test Result

4.5.3.3 Printing and Faxing Test Result

4.5.3.4 Disaster Recovery Test Result

4.5.3.6 Backup-and-Restore Test Results

4.5.3.7 Connectivity Test Result

4.5.4 Production Software LoadedSAP Services

4.1.4.3 PM Review Service Report

4.6 SAP Solution Management Optimization

4.7 SAP Operations Readiness Assessment

Possible impact / Tota



W B S

T i t l e

5 Go Live and SupportProgram, Project, Risk and Quality Management

5.1.1 Phase Startup




5.1.2 E/M /C Results


5.1.2.3 Change Log

5.1.2.4 Issue Log


5 1 2 6 Deliverable Acceptance Documents

5.1.4.2 PM Review Service Report



5.1.4.2 PM Review Service Report5.6.1 SAP GoingLive Check: Verification Session

5.7 SAP EarlyWatch Check

Possible impact



Purpose

CPI/Project Number

Customer Number

Program Manager

SAP Service Partner(s)

Attach individual Q-Gate assessment sheet here:

Project Sponsor Project Manager (Custome

Project Manager (SAP) Project Manager (Service P

Q

The Q-Gate Sign off is used by the Project Manager, The Project Team and the Client to

next phase of the project. This document should be updated and signed before moving

(go/acceptable/completed) category. The Q-Gates are either Red (stop), Yellow (caution

Project Identification

Project Name

Customer Name