(logo) (address)

Scope Baseline Document Proc. #:

Description PN-RG-Scope Baseline Revision #: 1.0 Page: 1 of 5

SCOPE BASELINE
Template: Scope Baseline-v1.1.dotx
Doc Name: ID-PN-RG-Scope Baseline-mmddyyyy-v#.docx

TICKET # PROJECT NAME BUSINESS PROCESS LEAD

JOB CODE PORTFOLIO NAME (REGION) BPL EMAIL

Choose an item.
DATE PROCESS MANAGEMENT IT PROJECT MANAGER
[Pick the date] PLANNING
AREA IT-PM EMAIL
PRODUCTION

TABLE OF CONTENTS
1. PURPOSE ........................................................................................................................................ 2
2. PROJECT SCOPE STATEMENT .............................................................................................................. 2
3. WORK BREAKDOWN STRUCTURE ......................................................................................................... 2
4. WBS DICTIONARY – WORK PACKAGES................................................................................................. 4
ID

4. SPONSOR ACCEPTANCE ..................................................................................................................... 5

 PN-RG-Scope Baseline-mmddyyyy-v#

1. Purpose
The Scope Baseline provides approved detail for project scope statement, WBS and dictionary of each work packages.

2. Project Scope Statement

The project scope statement details the project’s deliverables and the work necessary to create these deliverables.
 Product Scope Description – describes what the project will accomplish
 Product Acceptance Criteria – describes what requirements must be met in order for the project to be accepted as
complete
 Project Deliverables – detailed list of deliverables the project will result in
 Project Exclusions – description of work that is not included in the project and outside of the scope
 Project Constraints – lists limits on resources for time, money, manpower, or equipment (capital)
 Project Assumptions – describes the list of assumptions the project team and stakeholders are working under to
complete the project

3. Work Breakdown Structure

The WBS for the Project is comprised of work packages which do not exceed 40 hours of work but are at least 4 hours of
work. Work packages were developed through close collaboration among project team members and stakeholders with
input from functional managers and research from past projects.

The project schedule was derived from the WBS and Business Case with input from all project team members. The
schedule was completed, reviewed by the Project Sponsor, and approved and base-lined. The schedule will be maintained
as a MS Project Gantt Chart by the Release Coordinator. Any proposed changes to the schedule will follow IT-Production
change control process. If established boundary controls may be exceeded, a change request will be submitted to the
Release Coordinator and Production Manager.

The change boundary conditions are:

Cost Performance Indicator (CPI): Earned Value / Actual
Cost
Less than 1: Inefficient use of funds
More than 1: Efficient use of funds
Earned Value is also known as Budgeted cost of work
performed
Actual Cost is also known as Actual Cost of work
performed
Schedule Performance Indicator (SPI): Earned Value /
Planned Value
Less than 1: project will be late
More than 1: project will be early
Planned Value is also known as Budgeted Cost of Work
Scheduled

CPI less than 0.98 or greater than 1.0 and SPI less than 0.98 or greater than 1.0 reference to documents: Monthly Status
Report, First Tab and Project Closeout Report, First Tab.

If the change is approved by the Project Sponsor then it will be implemented by the Release Coordinator who will update
the schedule and all documentation and communicate the change to all stakeholders in accordance with the Change
Control Process.

The Project Schedule Baseline is provided in document Schedule Plan belongs to the actual project, Work Breakdown
Structure is provided in Appendix A.

Project Management 2 Scope Baseline Version 1.1

Production

Scope Baseline Document
Description
1. Initiation
1.1 Conduct Needs Analysis
• Create BAC ticket
• Review ERP tickets relate to the
release
• Review vendor release notes
• Create assess functionalties-E&F
• Determine potetial risk, issues and
impact
1.2 Collect Requirements
• Identify Project Artifacts
• Preliminary delivery timeline -
Scope Baseline
• Resource Requirements
Traceability Matrix
• Asses Project Cost - Scope Baseline
1.3 Desicion Point meeting
1.4 Update BAC ticket
1.5 Define roles, responsabilities &
Communication Plan
1.6 Update Production Release
Scheduler
1.7 Busines Case
1.8 Financial Work Order
(logo)
PN-RG-Scope Baseline
2. Planning
2.1 Create Project Plan
2.2 Create Project Status Report
2.3 Review Analysis Requirements
2.4 Develop Inventory of all Change
Impact
• Create Tech Change Plan
• Meet with Technical Change
Manager
• Meet with QA Manager
• Meet with Infrastructure Manager
2.5 Document Functional
Specifications BP
• Enhancements
• Fixes
2.6 Review Enhancements & Fixes
2.7 Kick off Meeting
2.8 Feedback
2.9 Incorporate feedback
• Business Process Change Plan
• Finance Applications Change Plan
2.10 Finalize Scope Baseline
2.11 Update Project Plan
2.12 Test Plans
• Determine Standards, Process &
Metricsa to measure Quality
Performance
• Create Deployment Tech Plan
2.13 Design QA Test Environment
• Review Tech Change Plan,Request Changes, Update QA & Production
Schedule
• Update Release Notes and Deployment Tech Plan
• Review and update Risk Issue Matrix
2.14 Finalize and Gain formal
approval of the Project Plan
Proc. #:
Revision #:
3. QA Testing
3.1 QA Testing Preparation
• Follow Test Traceability
Requirements Matrix EF
• Develop Testin/Scenario Scrips
(HPQC)
• Set up Test Management tool
(HPQC)
3.2 Testing Regression E Setup
• Determinar test environment code
requirement
• Receive Vendor Deployment Tech
Plan
• Create configuration document
• Enter Configuration
• Enter configuration for all integrated
systemsn
• Add users and appropriate security
3.3 Testing Regression Execution
• Execute test cases
• Data verification and validation
• Identify defects to product
specifications
• Assigned all defects and request
new code to vendor
• Modify code and re-test new code
3.4 Testing Functional E Setup
• Same of 3.2
3.5 Testing Functional Execution
• Same of 3.3
3.6 Close QA Testing
• Generate Report Test Result and Sign off
• Archive test data and release resources
(address)
1.0 Page: 3 of 5
4. UAT 5. Deployment 6. Close-out
4.1 UAT Preparation
5.1 CAB Meeting 6.1 Project Closeout Report
• UAT plan and sign off
• Develop UAT scrips
• Update deployment tech plan 6.2 Complete Identify Project Artifacts
5.2 Communicate to all Stakeholders
• Set up UAT environment tool and archive
(HPQC)
• Identify user group 5.3 Production Environment
6.3 Update Projec Plan, Lessons
Preparation
Learne3d, Project Documents and
4.2 UAT Environment Set up • Provide Infrastructure with Archive
deployment tech plan
• Follow deployment tech plan and
Tech change plan • IT set up hardware and apply
6.4 Distribuite to team members &
• Update configuration document application
release resources
• Enter configuration • System Configuration
• Configure middleware/integration
• Enter configuration for all integrated
endpoints
systems
• Apply security for end users
• Add users and appropriate sucurity
4.3 UAT Execution
5.4 Go-Life
• Execute tests - include business
process testing
• UAT execution reporting and sign off
5.5 Follow-up Meetings
4.4 Close UAT
• Determinar Workaround if required
• Meeting to obtain approval - Subtantial
completion
• Review open defect with B units
• Obtain sign off for deployment
• Finalize deployment tech plan by production
Appendix A - Figure 1.1, Work
Breakdown Structure (WBS)
 PN-RG-Scope Baseline-mmddyyyy-v#

4. WBS Dictionary – Work Packages

ID

Level WBS Code Element Name Description of Work Deliverables Resources

Received the release note Vendors
3 1.1.3 Vendor Release Notes Yes
from vendor
Assess Functionalities: Create the Test traceability QA Manager
3 1.1.4 Yes
Enhancements and Fixes requirements matrix - EF RC
Determine potential risk, IT Managers
Security: user name,
3 1.1.5 issues and impact (verify Yes RC
password, rights
security) BPL
Define preliminary delivery IT Managers
3 1.2.2 Review schedules Yes
timeline BPL / RC
Define activities, time, RC
3 1.2.3 Create Schedule Plan Yes
resources and budget
IT Managers
Define Roles, responsibilities Create Communication
3 1.2.6 Yes BPL
and communication channels Plan
RC
Production
2 1.6 Complete Business Case Yes
Manager
Complete Financial Work Production
2 1.7 Yes
Order Manager
Complete processes, RC
2 2.1 Update Project Plan Yes
business rules, all plans
2 2.2 Start Reporting Project Status Yes RC
3 2.4.1 Crate Tech Plan Meet all IT areas Yes All IT Managers
Document functional QA Manager
2 2.5 All enhancement and fixes Yes
specifications business process
2 2.7 Kick off meeting Yes All stakeholders
TPM
2 2.10 Finalize Scope Baseline Yes
RC
2 2.11 Update Project Plan Finalize the project plan Yes RC
3 2.12.1 Create Test Plan QA Test plan Yes QA Lead
3 2.12.2 Create Deployment Tech Plan Cutover plan Yes QA Tech
3 3.1.2 Develop Testing/Scenario Scripts Yes QA Lead
3 3.2.3/3.4.3 Configuration Document Creation Yes QA Lead
Data verification and QA Lead
3 3.3.2/3.5.2 Create status report Yes
validation QA Manager
QA Manager
Identify defects to product
3 3.3.3/3.5.3 Status Report Yes Vendors
specifications
Production M
Generate Status Report and QA Lead
3 3.6.1 Status Report Yes
sign off
3 4.1.1 UAT Plan and sign off Yes QA Lead
3 4.3.3 Status Report and sign off Status Report Yes QA Lead
3 4.4.2 Meeting Minutes Yes RC
Production M
4 4.4.2.2 Obtain sign off for deployment Yes
QA Lead / RC
3 4.4.3 Deployment Tech Plan By Production V 4 0 Yes RC / QA Analyst
Meeting Minutes Change M
2 5.1 CAB Meeting Yes
CAB Schedule

Project Management 4 Scope Baseline Version 1.1

Production
 PN-RG-Scope Baseline-mmddyyyy-v#

Level WBS Code Element Name Description of Work Deliverables Resources

Production M
Infrastructure
2 5.4 Go-Live Yes
Manager/TPM /
RC
Create and gain formal
2 6.1 approval of project closeout Project Closeout Report Yes RC
report
All document that the
2 6.2 Identify Project Artifacts Yes RC
process will generate
Lessons learned, project
2 6.3 Update Project Plan Yes RC
documents and archive

4. Sponsor Acceptance
I understand that by agreeing to participate in this project through the execution of the scope baseline, I approve
of the scope and activities defined and authorize my department to participate as documented for the successful
implementation of this application in our department.

NAME DATE SIGNATURE

1. PRODUCTION MANAGER _____/_____/_______

2. RELEASE COORDINATOR _____/_____/_______

3. QUALITY ASSURANCE MANAGER _____/_____/_______

4. BPL _____/_____/_______

Project Management 5 Scope Baseline Version 1.1

Production