SDLC Program Project Management

Get *ALL* 100+ Editable Word, Visio, HTML & Project Source Documents (500+ Files) Totaling 1000+ Printed Pages for Only $497 - Buy I.T. Now!

SDLC SOP 1000: Program /
Project Management

Objective:

The purpose of this Standard Operating Procedure (SOP) is to document the project management infrastructure, reporting relationships and project management activities. Program/Project Managers and the Program Management Office (PMO) deliver project management.

Scope

This SOP defines the SDLC project management process including structure, relationships and activities associated with the recognition, definition, design, implementation, testing, release, operation and management of a project.

Owner:

Chief Technology Officer

Sections:

i	Definitions
ii	Process Flow Diagrams
1	Roles and Responsibilities
2	Metrics
3	Program/Project Management Reporting Structure
4	Procedure Activities
5	Forms
6	Exceptions
7	Tools/Software/Technology Used
8	Attachments

Related SOP's:

1004	Configuration Management
1005	Release Planning
1040	Requirements Definition
1101	Training and Documentation

Get "IT"
ScalabilITy - ReliabilITy
FlexibilITy - AgilITy
LongevITy - QualITy
.doc .xls .ppt .mpp .vsd .htm EdITable; Policies, Processes, Procedures, Projects Tasks, Diagrams, Forms & Files.
DOWNLOAD
Satisfaction Guaranteed.

-->

SDLC Standard Operating Procedures:

SDLC Framework:

SDLC Gates:

SDLC Roles and Responsibilities:

SDLC Forms:

SDLC Templates:

SOP 1000 - Project Management Definitions

Term	Definition/Description
*Program/Project Management* .	The systematic execution of a System Development Life Cycle (SDLC) for a release or projects that have significant impact on an organization’s service delivery. This procedure oversees the SDLC execution; thus, it relies heavily on defined procedure activities and acceptance criteria for inputs and outputs Note: Every unit within SDLC interacts with Program/Project Management. Every release of new and enhanced features and functionality requires the commitment and effort from all departments.
*Project Manager*	The focal point throughout a project who ensures that the responsible party has completed with quality and comply with defined acceptance criteria. The *Project Manager* also acts as the conduit for communicating the ress of the project and decisions made throughout the process to the *Project Sponsor, Contracting Organization, and the Performing Organization*.
*Program Management*	Addresses oversight for a group of projects. *ram Managers* shoulder the responsible for the successful completion of Program objectives by supporting and developing project staff. Reporting at this level provides *Executive Management* with the information necessary to make informed decisions and execute actions that optimize benefits to the organization.
*Program Manager*	The tactical manager who facilitates, monitors and communicates the ress and issues in implementing the strategic objectives of an approved ram. The *ram Manager* works cross-functionally to develop the blueprint that integrates multiple release deliverables that enhance the ram’s portfolio.
*PMO*	The *PMO* is the organization that consolidates all project plans and reports the status to executive management. Impacts from individual projects can be seen from an organizational perspective and responded to rapidly. The *PMO* is where project and Program standards, procedures, policies and reporting are established.
*Business Gate*	defined milestone in a project lifecycle when specific requirements must be met in order to make or validate business decisions relating to the project.
*Lock-Down*	The milestone in a project schedule achieved when agreement exists between the Performing Organizations and the Contracting Organizations for the delivery of a defined project scope of work within a defined schedule at a defined cost.
*Management Phase Review*	An event associated with selected business gates where specific decisions concerning the project are made by appropriate levels of management. Deviations in deliverables or timeframe are handled by convening the Gate 6 Review Board. This group will make any decisions concerning scope, cost, and schedule tradeoffs. These business gates are: G-11: Project Strategy Lock-Down G-10: Requirements Scope Lock-Down G-6: Project Lock-Down G-4: Begin Validation G-2: Begin FOA G-0: General Availability
SDLC Business Gates	The foundation is Program/Project Management in the SDLC Business Gates. This Systems Development Life Cycle (SDLC) begins at project initiation and moves through deployment to the production environment.
*Phase*	A collection of logically related project activities, usually culminating in the completion of a major deliverable. The conclusion of a project phase is generally marked by a review of both key deliverables and project performance in order to determine if the project should continue into its next phase as defined or with modifications or be terminated and to detect and correct errors cost effectively.
*ram*	A defined set of projects containing common dependencies, and/or resources and/or objectives overseen by a Program Manager
*Project*	A temporary endeavour undertaken to create a unique product or service. A project has a defined scope of work (unique product or service), a time constraint within which the project objectives must be completed (temporary) and a cost constraint. In the context of SDLC, a project may be one of: an individual feature a collection of features making a release a collection of product releases making up a portfolio a new product development
*System Development Life Cycle (SDLC)*	A predictable series of phases through which a new information system resses from conception to implementation. All of the activities involved with creating and operating an information system, from the planning phase and/or the initial concept to the point at which the system is installed in a production environment. The major phases are Release Planning, Definition (Requirements and Specifications), Development, Test (Validation), and Deployment.

Process Flow Diagrams

Process Gates Overview

Click Image to Enlarge

ram Management Overview

Click Image to Enlarge

1. Roles and Responsibilities

*Role*	*Responsibili*ty
*Contracting Organization*	The Contracting Organization contracts with the performing organization to develop the product using a project discipline. The Contracting Organization represents two departments: Product and Technical Support. Product is divided into Sales and Advertising, Marketing and Product, and Strategic Development. A brief description of each area follows. Sales and Marketing: The area that sells to clients/customers in both the domestic and international markets. Marketing and Product: This area manages the portfolio of features and functionality for outbound marketing. Strategic Development: Research and Development group viewing opportunities in emerging markets and up-selling existing accounts. Technical Support: Technical Support performs two roles in the current environment: Training and customer support. As the Service Organization they provide customer support to end users (first level). In their role as the Training Organization they provide training to field and service engineers.
*Project Manager*	The focal point throughout a project who ensures that the responsible party has completed with quality and comply with defined acceptance criteria. The *Project Manager* also acts as the conduit for communicating the ress of the project and decisions made throughout the process to the *Project Sponsor, Contracting Organization, and the Performing Organization*.
*Customer*	A Customer is the individual or organization who will use the project product. Note that there is a distinction for SDLC between the true customer and the Contracting Organization that acts as the customer’s representative within SDLC
*Office of the Chief Executive (OCE)*	The Office of the Chief Executive is the executive management team at SDLC. They establish business strategy and commission projects.
*Owner*	The Owner oversees the completion of work at a gate. They may be from the Product, Content, Technical Support, or Development areas depending on the project activities underway. The Project Sponsor assigns owners at the beginning of a project. Each gate has an Owner who is accountable for tracking the gate requirements, maintaining the status of the gate and taking corrective action to ensure that the gate is met in a timely manner. The gate owner is also responsible for convening a meeting of the appropriate review board to approve passage of the gate. In the case of gates that have associated management phase reviews (see glossary), the gate owner convenes the review meeting and facilitates the decision making that is required at that gate. In the event that an exception arises at a gate that does not have any associated management phase review, the owner is responsible for escalating the issue to the appropriate management phase review board for resolution.
*Performing Organization*	The Performing Organization is generally the Engineering Department. The Engineering Department consists of Development (Sustaining, Advanced and Strategic), Validation/Quality Assurance, Operations (OCC, Release Engineering, Database Administration, Network and Operations Engineering), Systems Engineering/Architecture and project management.
*ram Manager*	The Program Manager is the individual who oversees multiple projects that are related by a type of service delivery or by feature and functionality. The ram Manager is accountable for the Program and is empowered by the Office of the Chief Executive to make decisions affecting the successful outcome of the ram. The Program Manager takes an enterprise view. The Program Manager is responsible for determining the schedule for deployment of company resources and achieving the objectives of a specific ram. The role includes the following additional responsibilities: Managing project managers Producing milestone ress reports Initiating issue and risk mediation Scheduling and conducting status meeting - Preparing status reports - Ensuring the project is on time, within budget Program deliverables.
*ram Management Office (PMO)*	The program Management Office (PMO) monitors, supports and reports on SDLC's rams and projects. Program Managers provide defined periodic updates to the PMO. The PMO consolidates the efforts of all rams and technology specific projects and delivers these reports to the OCE. The PMO is responsible for issuing standards and guidelines for planning, tracking, and reporting, and for providing project support to individual project teams. Accountability for project delivery will remain with the individual Project Manager and Program Manager.
*ram Manager*	The Project Manager is accountable for the project and must be empowered to make decisions affecting the successful outcome of the project responsible for managing a project. This should not be confused with the project management function that exists within many organizations. Project Managers are responsible for determining the deployment schedule for their specific project. This role includes the following additional responsibilities: Reviewing ress reports Taking corrective action in problem solving Scheduling and conducting status meetings Preparing status reports Ensuring that change control procedures are being followed
*Review Board*	The Review Board is composed of representatives from both the Performing and Contracting Organizations, as well as the Project Sponsor, Project Manager and Program Manager. Review Boards assess the deliverables at each gate in the System Development Life Cycle to insure that requirements have been met. Also, the Review Board’s specific knowledge of the project’s goals and status allow it to make informed decisions to which they are held accountable. Milestone/Gate reviews provide the mechanism for the management of the Performing Organization and the Contracting Organization to make decisions concerning the scope, cost and schedule of the project. At each review, the members of the Review Board are required to make decisions that are in the best interests of SDLC. These decisions may involve making tradeoffs to arrive at an optimal decision. It may be necessary to omit or remove scope in order to satisfy cost and schedule constraints. Additional cost may be approved to maintain scope and schedule commitments. A schedule delay may be agreed upon to enable required scope to be delivered within existing budgets. Each case is unique and must be considered on its specific merits.
*Service Organization*	The Service Organization is the unit that that provides deployment support services to the Contracting Organization for all SDLC products. Services include provision and support of deployment tools, software load support, problem resolution, phone support and deployment planning support. At SDLC the Service Organization is generally Technical Support.
*Training Organization*	The Training Organization is the organization that provides customer installation and operations training to the Contracting Organization for all SDLC products. This generally refers to Technical Support.

2. Metrics

Program/Project Management metrics are focused on the measurement of cycle times and defects. Measurements provide the foundation to quickly identify, isolate and remediate inefficient results from activities that do not meet expected performance levels.

*Metric*	*Description*
*Cycle Time*	The number of days or hours it takes to complete requirements for a SDLC Business Gate and/or milestone.
*Defects*	Instances of failure to pass specific tests or quality measures or to meet specification/acceptance criteria. These are recorded and assessed throughout a project and reported at the end of the project.
*Change Agents*	Individuals who analyze a process and recommend ways to improve it, successful or not in its adoption, will be reported to Engineering Department management. These individuals will receive recognition for their effort to compress cycle times and/or improve quality.

3. Program/Project Management Reporting Structure

The structure above represents a reporting structure, not an organization chart.

The Office of the Chief Executive is the executive management team at SDLC. It establishes business strategy and commissions projects. Project Sponsors are charged with developing a concept into defined requirements and scope, and ultimately ushering the defined deliverable through project milestones. ram Managers oversee a portfolio of projects ensuring their successful delivery and integration into the SDLC environment. Project Managers oversee the day-to-day execution of work of specific projects, ensure that acceptance criteria are met, and manage the gate Review Board activities.

Project ress, issues and risks are reported to ram Managers who oversee a portfolio of related projects. The ram Manager oversees escalation, mitigation and resolution of project barriers and delays whenever a Project Manager requires assistance. Program Managers provide ress reports to the ram Management Office where enterprise level project plans are produced and reviewed. Impacts across ram and projects are identified and reported by the ram Management Office.

Certain Engineering Department technical activities fall outside the activities specific to a project. These activities (e.g., hardware and software maintenance, tools and utilities, etc.) are reported directly to the Program Management Office. The Office of the Chief Executive assesses these time and resource requirements via the enterprise level project plan maintained by the PMO.

*Activity*	*Description*
*PMO Level Reporting*	PMO meets weekly with Program Managers to review status reports and share information about the activities of other projects and rams. The weekly Program Reports data are analyzed and used to prepare the OCE Status Report. The PMO presents the report to OCE members. The PMO attends OCE meetings to address concerns and solicit assistance for Program Manager requests for support and/or intervention. Action items from the OCE meeting are communicated to the PMO within 2 days (or as appropriate). As part of the OCE’s PMO Report technology projects outside of formal rams are reported upon. Prioritization and integration into the consolidated/enterprise project plan is determined. The PMO reports back to the technology Project Manager the results of the meeting.
*ram Level Reporting*	The Program Manager consolidates individual project reports from each reporting Project Manager into a Program Report for the PMO. Program Reports focus on the enterprise and as such present milestones, opportunities, risks and issues that are effecting efforts. In cases where OCE intervention is requested, course of action recommendations are included.
*Project Level Reporting*	Each week the Project Manager completes a Project report that is provided to the Program Manager. At weekly status meetings Program and Project Managers’ review the project report and strategize on approaches to address-identified risks and issues. Action items are developed and agreed to by the Program and Project Managers. These action items are tracked and reported on the weekly Project Report. Technology projects outside Program delivery are reported directly to the PMO by the technology Project Manager using the same reporting mechanism as above.

4. Procedure Activities

*Gate/Activity*	*Description*
*Click Image to Enlarge*
*G-12: Project Start*	Business Objective: Declare the start of the project. This gate is used to kick-off finalization of the feature set and project strategy. Owner: Program Sponsor Review Board: N/A
*Designate Program Sponsor and Project Manager*	Project Start begins with the designation of a Program Sponsor and Project Manager. The Program Sponsor is designated by OCE. The Program Manager assigns the Project Manager.
*G-11: Project Strategy Lock-Down*	Business Objective: Approve a set of features and project strategy Owner: Project Manager Review Board: Program Sponsor, Program Manager, Project Manager, Contracting Organization(s), and Performing Organization(s)
*Project Manager*	The Project Manager is responsible for ensuring that the documents indicated in the next activity are completed with quality and meet the acceptance criteria defined in the Release Planning Procedure (SOP 1005))
*Organizations:* *Project Sponsor* *Contracting* *Performing*	Program Sponsor (OWN) Project Strategy including: Timeline, R&D Budget, Affordability Percentage, Scope of Work definitions and Anchor Objectives. Contracting Organization (OWN) Market Requirements Scope of Work Performing Organization (OWN) High Level Effort Estimate
*Project Manager*	The Project Manager establishes a preliminary project plan incorporating the project strategy and high-level effort estimates received within this gate. Once the above documents are accepted by the receiving organization the Project Manager will call the Review Board to session and provide evidence that all requirements have been met for Gate 11.
*Review Board*	Establish project strategy and the initial project constraints of scope, cost and schedule utilizing such factors as R & D Budget, Affordability Models and Anchor Objectives. Upon approval, all materials are communicated to the Contracting and Performing Organizations. The communication is focused at the approved anchor objectives, project strategy, initial project constraints and scheduling. The Project Manager is responsible for communications to all participating project areas.
*Click Image to Enlarge*
*G-10: Requirements Scope Lock-Down*	Business Objective: Approve the Scope of Work for which the organization will commit to develop requirements. Owner: Project Manager Review Board: Program Sponsor, Program Manager, Project Manager, Contracting Organization(s), and Performing Organization(s)
*Project Manager*	The Project Manager is responsible for ensuring that the following documents are completed with quality and meet acceptance criteria defined in the Release Planning Procedure (SOP 1005). Contracting Organization (OWN) Initial Portfolio Scope Business Plan Impact Assessment Scope of Work Performing Organization (OWN) Project Resource Plan
*Review Board*	Review the results of the concept phase and commit to the definition and planning of a project. Target delivery windows may be established, but this does not constitute a commitment to deliver the project as it is defined at this point. The additional definition and planning which takes place during the definition phase will increase knowledge about the scope, cost and schedule of the project which may result in changes to any or all of those parameters.
*Review Board*	The Review Board’s acceptance of the approved documents by the Receiving Organization moves each SOW document to the Development Function of the Performing Organization for analysis.
*Project Manager*	The Project Manager ensures coordination between Contracting and Performing Organizations. Project Managers facilitate meetings and document meeting outcomes. This effort is focused at reducing cycle time and maintaining the highest level of common understanding between parties. Further, the Project Manager will refine the project plan incorporating data available.
*G-9: Definition Phase Plan Approved*	Business Objective: Approve the plan to execute the definition phase so that the project’s business requirements (scope, timeframe and cost) are met Owner: Project Manager Review Board: Program Sponsor, Program Manager, Project Manager, Contracting Organization(s), and Performing Organization(s)
*Project Manager*	The Project Manager is responsible for ensuring that the following documents are completed with quality and meet acceptance criteria defined in the Requirements Definition Procedure (SOP 1040). Plan for the Definition Phase – Owner: Project Manager
*Organizations:* *Performing* *Contracting*	In order to complete the plan for the Definition Phase, the Project Manager requests and receives the items listed below from various areas of both the Contracting and Performing Organizations. Acceptance criteria for each item listed are defined in the Requirements Definition Procedure (SOP 1040). Contracting and Performing Organizations (CON) Detailed Schedule Resources/Costs Assigned Capital Budget Risk Plan Developed Validation Function of the Performing Organization (CON) Quality Plan Operations Function of the Performing Organization (CON) Configuration Plan
*Project Manager*	The deliverables for G-9b contribute to the development of the project’s communication plan and project plan by the Project Manager. At this point the Project Manager ensures that all known assumptions, dependencies, constraints, and risks are reflected in the project plan. The Project Manager sends recommendations to minimize the impact from assumptions, dependencies, constraints, and risks to the Program Sponsor. The Program Sponsor supports the resolution and/or mitigation of project barriers by working with OCE and/or Unit Managers.
*Click Image to Enlarge*
*G-8: System Requirements Definition Approved*	Business Objective: Obtain approval of the system requirements definition(s) from the Contracting Organization(s). Owner: Project Manager Review Board: Program Manager, Project Manager, Contracting Organization(s), and Performing Organization(s)
*Project Manager*	The Project Manager facilitates the dialog necessary between all parties that participated in the definition of SOW documents for the Development Function of the Performing Organization to complete Systems Requirements Specifications. The Project Manager has responsibility for ensuring full disclosure of features, functionality and technical constraints that impact the project scope approved at Gate 10.
*Review Board*	The Review Board reviews the approved System Requirements Specifications.
*G-7: Lock-Down Level Estimates Complete*	Business Objective: Complete the estimates and scope refinement necessary for Lock-Down. Owner: Project Manager Review Board: Program Manager, Project Manager, Contracting Organization(s), Architecture Function of the Performing Organization(s), and Development Function of the Performing Organization(s)
*Project Manager*	The *Project Manager* is responsible for ensuring that the documents in the next activity are completed with quality and meet acceptance criteria defined in the Requirements Definition Procedure (SOP 1040).
*Organizations:* *Performing* *Contracting*	Performing Organization (OWN) Refined Resources Estimates Architecture Function of the Performing Organization (OWN) Estimation Documentation Development Function of Performing Organization (OWN) Work Breakdown Structure Contracting Organization (OWN) Final Portfolio Scope
*Project Manager*	The Project Manager ensures coordination between Contracting and Performing Organizations. This effort is focused at reducing cycle time and maintaining the highest level of common understanding between parties. Further, the Project Manager will refine the project plan for the release incorporating data provided through this gate. The Project Manager will communicate the final portfolio scope to all interested areas in the organization
*Click Image to Enlarge*
*G-6: Project Lock-Down* *(Also described as: Go/No Go Decision or Cross-functional Commitment to the Delivery of a Defined Set of Features and Functionality)*	Business Objective: Obtain commitment between the Performing Organization(s) and the Contracting Organization(s) for the delivery of a defined project scope of work within a defined timeframe. (This scope is a refinement of the G-10 scope/plan). Owner: Project Manager Review Board: Program Sponsor, Program Manager, Project Manager, Contracting Organization(s), Performing Organization(s), and Service Organization
*Project Manager*	The *Project Manager* is responsible for ensuring that the documents in the next activity are completed with quality and meet acceptance criteria defined in the Requirements Definition Procedure (SOP 1040).
*Organizations:* *Project Manager* *Contracting* *Performing*	Project Manager (OWN) Project Plan Contracting Organization (OWN) Deployment Plan Business Plan Impact Assessment Performing Organization (OWN) Service Plan
*Project Manager*	In order to complete the project plan, the Project Manager will request and receive materials listed in G-6d from various areas of both the Contracting and Performing Organizations. Acceptance criteria for each item listed are defined in the Requirements Definition Procedure (SOP 1040).
*Organizations:* *Contracting* *Performing*	Contracting and Performing Organizations (CON) High Level Schedule Through Release General Availability Assigned Resources/Cost Profiles Through Release General Availability Risk Plan Release Scope Program Sponsor, Contracting and Performing Organizations (SUP) Approved Capital Budget QA Function of the Performing Organization (CON) Quality Plan Operations Function of the Performing Organization (CON) Configuration Plan.
*Review Board*	The Review Board reviews the results of the definition phase and re-evaluates the business objectives of the project. This review may result in agreed upon changes in scope, cost and/or schedule. The resulting agreement represents a commitment between the Performing and Contracting Organizations to deliver the project as defined within the agreed upon scope, cost and schedule constraints.
*Project Manager*	The Project Manager ensures coordination between the Contracting and Performing Organizations. Further, the Project Manager communicates the project scope and schedule to all interested parties.

*G-5: Detailed Plans Complete*	Business Objective: Approve the detailed project plan and commit the appropriate resources to execute the plan. Owner: Project Manager Review Board: Project Sponsor, Program Manager, Project Manager, and Performing Organization
*Project Manager*	The Project Manager is responsible for ensuring that the documents in the next activity are completed with quality and meet acceptance criteria defined in the Detail Design Procedure (SOP 1041).
*Performing Organization*	Development Function of the Performing Organization (OWN) Project Plan Product Functional Specification Architecture Function of the Performing Organization (OWN) Allocated Requirements System Interfaces The Architecture Function of the Performing Organization includes the Development and Operation Functions since they share responsibility for delivery and support of the delivered solution. Development handles the creation of the interface code. Operations manages the receipt, processing and storage or interface data; this includes service level considerations for capacity, turnaround time, and connectivity.
*Project Manager*	In order for the Project Manager to complete the project plan, he/she will use the project plan from the Development Function of the Performing Organization to update the overall project plan. Acceptance criteria are defined in the Detail Design Procedure (SOP 1041).
*Click Image to Enlarge*
*G-4: Begin Validation*	Business Objective: Ensure that the product meets the defined project scope and that the quality of the product is at an acceptable level to proceed to the Validation phase. Owner: Validation Function of the Performing Organization(s) Review Board: Program Manager, Project Manager, Validation function of the Performing Organization(s), and Development Function of the Performing Organization(s)
*Project Manager*	The Project Manager is responsible for ensuring that the documents and actions in the next activity are completed with quality and meet acceptance criteria defined in the Release Planning (SOP 1005), Training and Documentation (SOP 1101) and Quality Function procedures (SOP 1210).
*Performing Organization*	Development Function of the Performing Organization (OWN) Product (contains all defined scope and under configuration management) Development testing results Systems integration results Preliminary product documentation Field performance criteria Validation Function of the Performing Organization (OWN) Test preparation complete Note: Gate 4 requires a formal management review by the Performing Organization.
*Review Board*	Before commencing validation, the quality of the product and documentation emerging from the development phase is evaluated by the Review Board to assess the risk associated with entering the next phase. The level of management involved at this review may be lower than at the other management phase reviews since the issues being addressed at this review are internal to the Performing Organization. A key consideration at this review is to determine whether the product and documentation quality is high enough to allow the testing function to make significant ress. It is also possible at this review that decisions may need to be made concerning scope, cost and schedule tradeoffs if the project performance to date has deviated from the baseline established at G-6. Such decisions should not, however, be deferred until this point in the project’s lifecycle but should be actively addressed as soon as the need for a decision becomes apparent. At any point in the life cycle, if there are decisions concerning scope, cost and schedule tradeoffs, the Gate 6 Review Board will formally review the situation.
*Project Manager*	Should the Gate 6 Review Board need to assemble, the Project Manager is responsible for scheduling, notifying participants, creating meeting materials, facilitating meetings and distributing meeting minutes for this formal Review Board meeting. The Project Manager updates any resulting changes to the project plan. This may lead to the request and collection of revised estimates from Performing, Contracting, and Service Organizations.
*Click Image to Enlarge*
*G-3: Begin System Certification* *(Product Acceptance Testing)*	Business Objective: Approve release of the product to System Certification Testing. Owner: Contracting Organization(s) Review Board: Program Manager, Project Manager, Contracting Organization(s), System Certification Function of the Contracting Organization(s), and Validation Function of the Performing Organization(s)
*Project Manager*	The Project Manager is responsible for ensuring that the validation testing in the next activity is completed with quality and meets acceptance criteria defined in the Training and Documentation Procedures (SOP 1101) and Quality Function Procedures (SOP 1210).
*Validation Function of the Performing Organization*	The Validation Function of the Performing Organization completes a review and validation of the Preliminary Documentation provided by the Development Function of the Performing Organization. Acceptance by the Validation Function of the Performing Organization is required prior to beginning system certification.
*Project Manager*	The Project Manager has responsibility for verifying completion and obtaining signoff from the Validation Function of the Performing Organization.
*Click Image to Enlarge*
*G-2: Begin FOA/Beta* *(Client Acceptance Testing)*	· Business Objective: Approve release of the product for first office application. · Owner: Contracting Organization(s) · Review Board: Project Sponsor, Program Manager, Project Manager, Contracting Organization(s), System Certification Function of the Contracting Organization(s), Performing Organization(s), Validation Function of the Performing Organization(s), and Service Organization
*Project Manager*	The Project Manager is responsible for ensuring that the documents and actions in the next activity are completed with quality and meet acceptance criteria defined in the Quality Function Procedure (SOP 1210).
*Organizations:* *Performing* *Contracting* *Support* *Training*	Development Function of the Performing Organization (OWN) Product and Documentation Validation Function of the Performing Organization Product and Documentation test results Contracting Organization Certification test results Implementation Deployment Plan Deployment Plan Customer Site Market Analysis Training Organization Service Training Service Organization Deployment Tools
*Review Board*	Gate 2 requires a formal management review. The Deployment Phase represents a significant milestone to the customers in the lifecycle of a project. There is also significant risk associated with this milestone. The project product is expected to be of commercial quality at this time and any data from the validation phase that indicates otherwise must be carefully analyzed in terms of its potential impact to the selected customer site. Options at this review include approval to deploy the project product, approval to deploy with exceptions due to some subset of the scope having failed validation, and approval of a schedule delay (and consequent additional cost) to correct problems that are known to exist.
*Project Manager*	Deviations in deliverables or timeframe are handled using a formal process with the results communicated by the Project Manager to all areas participating in the effort. Any decisions concerning scope, cost and schedule tradeoffs, the Gate 6 Review Board shall formally review the situation. Should the Gate 6 Review Board need to assemble, the Project Manager is responsible for scheduling, notifying participants, creating meeting materials, facilitating meetings and distributing meeting minutes for this formal Review Board meeting. The Project Manager updates any resulting changes to the project plan. This may lead to the request and collection of revised estimates from Performing, Contracting, and Service Organizations.
*Click Image to Enlarge*
*G-1: Begin Controlled Rollout*	Business Objective: Approve the release of the product for controlled rollout. This gate is only required when a controlled rollout (CRO) is planned as an integral phase of the project. Owner: Contracting Organization(s) Review Board: Project Sponsor, Program Manager, Project Manager, Contracting Organization(s), Performing Organization(s), and Service Organization
*Project Manager*	The *Project Manager* is responsible for ensuring that the documents and actions in the next activity are completed with quality and meet acceptance criteria defined in the Training and Documentation (SOP 1101) and Deployment and Post Implementation procedures.
*Organizations:* *Contracting* *Performing*	Performing Organization (OWN) FOA test results Service training Client acceptance Contracting Organization (OWN) Implementation Deployment Plan Customer Site Marketing Analysis Risk Mitigation Plan
*Project Manager*	Since a controlled rollout occurs in the production environment, the documents in G-1b must meet quality and acceptance criteria defined in the Training and Documentation (SOP 1101) and Deployment and Post Implementation Procedures (SOP 1220). When a controlled rollout is an integral phase of the project plan it is mandatory, otherwise, this gate is optional.
*Click Image to Enlarge*
*G-0*	Business Objective: Approve the release of the product for general availability. Owner: Contracting Organization(s) Review Board: Project Sponsor, Program Manager, Project Manager, Contracting Organization(s), Performing Organization(s), and Service Organization
*Project Manager*	The *Project Manager* is responsible for ensuring that the documents and actions in the next activity are completed with quality and meet acceptance criteria defined in the Deployment and Post Implementation procedures (SOP 1220).
*Organizations:* *Contracting* *Service* *Performing* *Training*	Contract Organization (OWN) Product and Documentation Deployment plan complete Marketing information Market Analysis Risk Mitigation Plan Service (OWN) General Availability Implementation Deployment Plan Template Performing (OWN) Service training FOA test results Order entry system Client acceptance Training (OWN) Customer Training
*Review Board*	Gate 0 requires a formal review process. It is the final management phase review that occurs upon completion of initial field deployments (First Office Application and Controlled Rollout) which are intended to provide final validation of the project product in a live system environment. This review effectively marks completion of the project and acceptance by the Contracting Organizations from the Performing Organization. The Review Board reviews and approves completion of the Gate 0 requirements. Deviations in deliverables or timeframe are handled by convening the Gate 6 *Review Board*. This group will make any decisions concerning scope, cost, and schedule tradeoffs.
*Project Manager*	Should the Gate 6 *Review Board* need to assemble, the *Project Manager* is responsible for scheduling, notifying participants, creating meeting materials, facilitating meetings and distributing meeting minutes for this formal *Review Board* meeting. The *Project Manager* updates any resulting changes to the project plan. This may lead to the request and collection of revised estimates from *Performing, Contracting, and Service Organizations. The Project Manager* is responsible for attending the Program/Project Management post implementation review on the project and holds a meeting with other *Program* and Project Managers to review lessons learned. Trends and issues encountered over a number of projects are discussed as wells as new techniques that proved successful.
*Performing Organization*	The *Validation Function* of the Performing Organization conducts a project post-implementation review in which representatives from all areas participating in the project review the project. Quality issues and their root cause are discussed. The Quality Assurance group documents the post implementation meeting and distributes to all attendees, *all Project Managers* and *ram Managers* as well as the *PMO*.