Select Page

At this point in the process, you need to help recognize different contract types and make the right selection for the turnaround project. As the consultant for Project Revive LLC, your final task will be to create the statement of work (SOW) that describes the expectations for the new employee orientation product the third-party vendor will provide. Note: the various resources needed for this assessment are linked below.Although you have a lot of experience preparing statements of work, has not completed this part of the procurement process before. So, as part of your services, you will guide through this process. Your task is to help your client recognize the benefits of a good SOW and the risks associated with a “poor” SOWPart 1: Project Contract AnalysisDeliverable: Develop a decision matrix, select a contract for your turnaround project, and provide a rationaleDevelop a decision matrix to determine the best type of contract for the project considering the circumstances, timing requirements, budget availability, market conditions, and availability.Select a contract for this project and explain your selection.Part 2: Statement of Work (SOW) AnalysisDeliverable: Create a statement of work (SOW) for the turnaround project.Prepare a contract statement of work (SOW) describing the product or service to be supplied by a third-party vendor.The statement of work is your opportunity to clearly communicate your requirements and expectations. Refer to similar products on the Internet for realistic information to use in your statement of work.You may wish to use this optional Statement of Work Template [DOC] to complete this task.You may use other formats, if the information thoroughly addresses the expectations and requirements of the product or service.The SOW should address the following aspects related to the product or service to be procured:Specifications.Approach.Scope.Roles and responsibilities.Product and deliverables schedule.Deliverables and costs.Change control.Acceptance management.Quantity.Quality standards.Performance data.Work location.Period of performance.Contract to be used.PreparationUse the software of your choice to develop the deliverables for this assessment.This assessment has two deliverables:Develop a decision matrix, select a contract for your turnaround project, and provide a rationale.Create a statement of work (SOW) for the turnaround project.Deliverable FormatReferences: There is no set number of references required for this assessment. Use scholarly or academic sources where applicable.Format:Microsoft Project is not required for this assessment. This assessment has two parts and two deliverables.Use your choice of MS Word, MS Visio, or MS PowerPoint to develop the comprehensive analysesThese analyses are professional documents and should therefore follow the corresponding Academic and Professional Document Guidelines [PDF], including single-spaced paragraphs.Use APA style and format for references and in-text citations.




Unformatted Attachment Preview IT Governance
The following is an excerpt from the IT Governance.
Below you will find the IT policies for the Service Oriented Architecture and Enterprise, which is
the basic framework and structure for all IT-related activities and customer and user interactions
at The philosophy here is service centered on customer satisfaction and
IT Governance Overview
Governance policies provide guidelines to manage all IT programs and projects. Governance
establishes clear roles, responsibilities, and accountabilities for all project team members
including executive leadership and project managers. Industry best practices include the use of
a governance process to oversee and manage project spending and to ensure there is an
acceptable benefit or return on investment in all initiatives.
The key to the IT governance is the creation of the IT Program Management
Office (PMO). The PMO seeks to understand and integrate organizational business goals with
all approved project definitions and objectives. The PMO has a set definition and objectives,
which set the scope and boundaries to deliver project management methodologies, guidelines,
training, and investment benefits.
IT Service Oriented Governance Policies
The following types of policies apply to all service-oriented IT projects.
1. Project life cycle (design, development, and implementation) policies.
2. Quality management policies.
3. Configuration and change management policies.
All projects will have to adopt the project management office (PMO) quality management plan
and policies. Project change requests must go through the process and gain approval of the
change control board (CCB).
Amendment History – Document Status (Release #7, 2008)
Version #
Section, Page(s)and Text
Governance overview
PMO definition update
PMO Quality Management Discipline and Policies
The project management office (PMO) upholds the IT service-oriented architecture and
enterprise, which is the basic framework and structure for all IT-related activities and projects.
The philosophy is service, centered on customer satisfaction and quality.
The PMO provides training and the quality management discipline to plan and control through
testing and continuous improvement to ensure that each project satisfies the needs for which it
was undertaken (PMBOK® measure of quality).
The scope of quality management includes the following:
• Quality planning.
• Quality control.
• Quality assurance.
These quality elements interact with each other and with each of the project management
Concept Map of PMO Quality Management Tools and Techniques (Project
Management Institute, 2004)
*Benefit/Cost Analysis
*Design of Experiments
*Cost of Quality
*Quality Policy
*Quality Management
*Scope Statement
*Product Description
*Standards and
*Other process
*Inputs to other
The project management office:

Identifies the requirements that will satisfy the needs of the project.
Identifies which quality standards are relevant to the project such as ISO 9001:2000 and
Measures and monitors specific project outputs to determine if they comply with relevant
project quality metrics and standards and comply within the variance thresholds.
Tests, evaluates, and validates all project outputs and overall project performance.
Documents quality management strategies and measurements that can be collected,
reviewed, and archived for reference in future projects.
Guidelines and Procedures
Review project scope and deliverable specifications.
Assemble organization quality policies, standards, and
Describe process using inputs and outputs in particular
team disciplines (tools and techniques).
PM and project team
Analyze outputs from steps 1, 2, and 3 and create a list
of operational definition of quality.
PM and project team
Compile items in a list and sort into logical groupings.
PM and project team
Create the checklist that various project team members
can use to inspect quality.
PM and project team
Develop a quality statement on how quality
management and quality plan will be implemented.
PM and project team
Develop a quality control procedure on how to examine
specific project results to see if they comply with the
quality standards and to identify means to eliminate any
error or unsatisfactory results.
Quality audit team
Establish quality assurance by evaluating project
performance on a regular basis to provide confidence
that the project will satisfy the quality standards
previously set.
Quality audit team
Quality Assurance Template
Quality Assurance Plan for [Project Name]
Prepared by:
1.0 Draft quality assurance plan.
1.1 Introduction.
1.2 Purpose.
1.3 Policy statement.
1.4 Scope.
2.0 Management.
2.1 Organizational structure.
2.2 Roles and responsibilities.
2.2.1 Technical monitor/senior management.
2.2.2 Task leader.
2.2.3 Quality assurance team.
2.2.3 Technical staff.
3.0 Required documentation.
4.0 Quality assurance procedures.
4.1 Walkthrough procedure.
4.2 Review process.
4.2.1 Review procedures.
4.3 Audit process.
4.3.1 Audit procedures.
4.4 Evaluation process.
4.5 Process improvement.
5.0 Problem reporting procedures.
5.1 Noncompliance reporting procedures.
6.0 Quality assurance metrics.
Quality assurance check list forms.
Configuration and Change Management Policies
All projects will have to adopt the project management office (PMO) change control system
process and procedures. Project change requests go through the process and approval of the
change control board (CCB).
PMO’s change control system is a formal process with documented procedures that defines
how a project Scope Statement (original, defined, and signed by project sponsors) must be
maintained when the need for changes occur. The process includes steps by which the official
Project Scope Statement document may be changed. The process also includes all
electronic/paperwork tracking systems, processes, and approval levels necessary for
authorizing changes.
Concept Map of PMO Change Control Tools and Techniques (Project
Management Institute, 2004)
*Scope Change Control
*Performance Measurement
*Additional Planning
*Change Requests
*Scope Management
*Scope Changes
*Corrective Action
*Lessons Learned
*Adjusted Baseline
Completing a change-request form template is a requirement for this process. User (Change)
requests are submitted to the change control board (CCB) for approval.
Change Request Form Template
Project Name:
Date Request Submitted:
Title of Change Request
Change Order Number:
Submitted by: (name and contact information)
Change Category:
 Scope
Cost Technology Other
Description of change requested:
Events that made this change necessary or desirable:
Justification for the change/why it is needed/desired to continue/complete the project:
Impact of the proposed change on:
Suggested implementation if the change request is approved:
Required approvals:
Project Management Institute. (2004). A guide to the project management book of knowledge
(3rd ed.). Newtown Square, PA: Author.
Schwalbe, K. (2007). Information technology project management (5th ed.). Boston: Thomson.
Project Charter
Project Title: New Employee Orientation
Project Start Date: 10/09/2007 Projected Finish Date: 01/22/2008
Budget Information: $25,000.00
Project Manager: Jeremy Lee ext 8000
Project Objectives
To build an employee orientation learning module for the Human Resource department.
It will be accessed through the company Intranet. This module will include at least one
quiz and a signoff to document that new employees have completed their orientation and
understood the training information.
The following is a list of milestones which represent success on this project
• Kickoff meeting.
• Requirements and Project Planning.
• Design and Development.
• Testing.
• User Testing.
• Stakeholder testing and presentation.
• Design changes based upon testing information.
• Final Integration Testing.
• Roll out.
• Project Close.
Roles and Responsibilities
Organization /
Contact Information
Project sponsor
Jennifer Beal
Project Sponsor
Phone: X8999
Project manager
Jeremy Lee
Project Manager
Phone: X8000
Team resource
Alice Yee
Software Specialist
Phone: X8888
Page 1 of 2
Team resource
Tom Johansen
Phone: X8777
Team resource
John Sachs
QA Administrator
Phone: X8666
HR Manager
Phone: X8555
Sign-off: The stakeholders initialed their names in table above.
Comments: None.
Page 2 of 2
Quality Statement
Jennifer Beal, Alice Yee, Cheryl Gladstone, John Sachs, and Tom Johansen
From: Jeremy Lee
Re: NEO Project Quality Statement
PMO Quality Management Discipline and Policies
The PMO upholds the IT Service Oriented Architecture and Enterprise which is the basic
framework and structure for all IT-related activities and projects. The philosophy is service,
centered on customer satisfaction and quality.
NEO Project will implement and abide by the PMO Quality Policies. Quality Policies will be
implemented from the planning phase and throughout the different project phases to project
Ensuring Process Quality
Attention will be given to detailed documentation of the development process.
Program code test and review meetings will be scheduled regularly to make the processes flow
run smoothly and eliminate any misunderstandings from the team.
Exit phase meetings will be scheduled for documentations and lessons learned for future use.
Internal audits will be performed regularly. These are done not only for IT processes, but also
for Finance and Human Resources as well.
Quality Control
Testing Techniques

Expert Review
Testing Cycles

Unit testing
Integration testing
System testing
User acceptance testing
Page 1 of 2
NEO Project will comply with the PMO quality policies and guidelines. The Project Manager will
make sure all the project team and all resources are in compliance with these strict policies and
Jeremy Lee
Signed by PM
Page 2 of 2
Project Scope Statement
Version History
Project Name:
Project NEO
Prepared by:
Jeremy Lee
Date (MM/DD/YYYY):
approved Project Scope
Executive Summary
The Scope of this project is to design an employee orientation module as requested by the
Human Resource department to be used for new employee orientation. The information needs
to be accessed through the company Intranet where new employees would review all company
policies, take a quiz, and sign off on the new employee orientation process. The scope also
includes successful testing and acceptance by the Human Resource department.
Business Objectives
2.1 Product Description (Solution)
A New Employee Orientation Module for the Human Resource department will
be designed that can be accessed using the company Intranet for new employee orientations.
During the orientation process, new employees will review the presentation presented by
Human Resources followed by a quiz and sign off the orientation process.
Business Objectives
The Human Resource department would like to automate the new employee orientation process
by providing electronic documentation for orientation presentations, and maintain this database
to track and document successfully completed orientations.
Project Description
Project Scope
3.1 Project Scope
Includes (list Deliverables):
• Design a web based Human Resource module for new employee orientations.
• Integrate HR module with the company Intranet.
Page 1 of 5

Migrate existing hard copy presentations into electronic format.
Create quiz to assess new employees on their understanding of HR processes.
Create electronic sign-off for a successfully completed orientation.
Create online help to assist new employees during the orientation process.
Provide documentation to the Human Resource department to help with future changes
to the orientation material.
Does Not Include
The scope of this project does not include anything that is not maintaining the website
3.2 External Dependencies
All project requirements including the hard copy documents of the orientation material to be
promptly provided by Cheryl Gladstone.
3.3 Assumptions
All necessary hardware and software is already in place. The Employee
Orientation module will be created and integrated into the Human Resource section of the
3.4 Constraints
No new requirements to be added by the sponsors without affecting the project timeline and
Project Milestone

Target Date
Project Start
Project Charter
Work Breakdown Structure
Project Scope Statement
Project Schedule
Responsibility Assignment Matrix
Project Schedule Resources
Project Cost Estimate
Project Quality Statement
Stakeholder Analysis
Communication Plan
Risk Matrix
Final Project Plan
Software Orientation Learning Module Complete
Final Integration Testing Complete
Page 2 of 5

Documentation provided to Human Resource department
Training Human Resource on new module complete
Project Complete
Post Mortem Lessons Learned
Project Approach
5.1 Primary Plans
The project will have the following formal written plans:
• Project schedule. A firm schedule of events will be provided when all the requirements
have been satisfactorily met.
• Cost Estimate. Cost estimates will also be provided when all requirements are met.
• Responsibility Assignment Matrix.
• Quality Statement. A list of quality objectives is provided in the Quality Statement.
• Communication Plan. A spreadsheet of the communication plan is provided in the
Communication Management Section.
• Risk Analysis. A probability of risk associated with the project will be provided.
• Change Management. The change control procedures are included in the project plan.
Briefly describe how each of the following will be handled. Provide links to relevant documents
as appropriate. Modify example text provided or enter your own.
5.2 Change Management
The change control procedures as documented in the Change Management Plan will
be consistent with the Project Management Methodology and consist of the following processes:
• A Change Request Log will be established by the Project Manager to track all changes
associated with the project effort.
• All Change Requests submitted via Change Request Form will be assessed to
determine possible alternatives and costs.
• Change Requests will be reviewed and approved by the project owner.
• The effects of approved Change Requests on the scope and schedule of the project will
be reflected in updates to the Project Plan.
• The Change Request Log will be updated to reflect current status of Change Requests.
5.3 Communication Management
The following strategies have been established to promote effective communication within and
about this project. Specific Communication policies will be documented in the
Communication Plan.
Page 3 of 5

The Project Manager will present project status to the project Sponsors on a weekly
basis; however, ad hoc meetings will be established at the Project Manager’s discretion
as issues or change control items arise.
The Project Manager will provide a written status report to the project Sponsors on a
monthly basis and distribute the Project Team meeting minutes.
The project Sponsors will be notified via e-mail of all urgent issues. Issue notification will
include time constraints, and impacts, which will identify the urgency of the request for
The Project Team will have weekly update and status meetings to review completed
tasks and determine current work priorities. Minutes will be produced from all meetings.
All electronic Project Documents will be maintained in central storage accessible by all
project stakeholders.
5.4 Resource Management
The project team will produce a Resource Management Plan that will document the following:
• Lists all major goods and services required in the project along with cost estimates and
quality information.
• Indicates which goods and services will be obtained from sources outside the
• Indicates who is assigned to the project and when.
The Scope Statement is approved by the:
• Project Sponsor
Jennifer Beal
• Project Manager
Jeremy Lee
Project performance baseline changes will be approved by the:
• Project Sponsor
Jennifer Beal
• Project Manager
Jeremy Lee
Project deliverables will be approved or accepted by the:
• Project Sponsor
Jennifer Beal
• Key Stakeholders
Cheryl Gladstone
Specific task responsibilities of project resources will be defined in the Responsibility
Assignment Matrix.
Project Scope Statement Approval / Signatures
Project Name:
NEO Project
Project Manager:
Jeremy Lee
The purpose of this document is to provide a vehicle for documenting the initial planning efforts
for the project. It is used to reach a satisfactory level of mutual agreement between the Project
Page 4 of 5
Manager and the Project Sponsors and Owners with respect to the objectives and scope of the
project before significant resources are committed and expenses incurred.
I have reviewed the information contained in this Project Scope Statement and agree:
Jeremy Lee
Project Manager
Jennifer Beal
Project Sponsor
Cheryl Gladstone
HR Manager
The signatures above indicate an understanding of the purpose and content of this document by
those signing it. By signing this document, they agree to this as the formal Project Scope
Statement document.
Page 5 of 5

Purchase answer to see full