Beruflich Dokumente
Kultur Dokumente
Volume
ProjectManagement
Guide
ISS P R OG R A M M A N AG EM E N T & GOV ER N A N C E O FFIC E
37 Executive Drive,
Danbury, CT 06801
Table of Contents
Table of Contents.............................................................................................................i
Introduction.....................................................................................................................1
ISS PMO Work Definitions..............................................................................................2
ISS PMO Functions and Role.........................................................................................4
Applications & ISS interactions.....................................................................................7
Project Categorization.....................................................................................................8
Project Roles and Responsibilities ...............................................................................10
Program Management Office (PMO)......................................................................................10
PMO Representative (PMO Rep)............................................................................................10
Project Team...........................................................................................................................10
Project Sponsor.......................................................................................................................12
Customer.................................................................................................................................13
Stakeholders...........................................................................................................................14
Vendors...................................................................................................................................14
Steering / Stakeholder Committee .........................................................................................14
ISS PMO Project Management Processes....................................................................16
Pipeline Process Flow................................................................................................17
...................................................................................................................................17
Process Definition...................................................................................................................18
Process Objectives.................................................................................................................18
Begins When...........................................................................................................................18
Includes...................................................................................................................................18
Excludes..................................................................................................................................18
Ends........................................................................................................................................18
Post-Pipeline Acceptance process................................................................................20
Initiation Phase...........................................................................................................20
Initiation Phase Flow...............................................................................................................22
Process Definition...................................................................................................................23
Task Deliverables list..............................................................................................................25
RICAP Chart ...........................................................................................................................26
Phase Completion Checklist...................................................................................................27
Planning Phase.............................................................................................................28
Planning Phase Flow..............................................................................................................29
Process Definition...................................................................................................................30
Task Deliverables list..............................................................................................................32
RICAP Chart ...........................................................................................................................33
Phase Completion Checklist...................................................................................................34
Execution & Controlling Phase ..................................................................................35
Execution & Controlling Phase flow........................................................................................36
Process Definition...................................................................................................................37
Task Deliverable List...............................................................................................................39
RICAP Chart............................................................................................................................40
Phase Completion Checklist...................................................................................................41
Close-out Phase ........................................................................................................42
Turnover to Operation.............................................................................................................42
Post-Implementation Review .................................................................................................42
Administrative Closeout..........................................................................................................43
Close-out Phase flow..............................................................................................................44
Process Definition...................................................................................................................45
Task Deliverables List.............................................................................................................46
RICAP Chart ...........................................................................................................................46
Phase Completion Checklist...................................................................................................47
Scope Management......................................................................................................47
Introduction.................................................................................................................48
Priority .......................................................................................................................48
Impact.........................................................................................................................48
Scope Change Process..............................................................................................49
Scope change for Fast track work...........................................................................................49
Scope change for standard & complex work...........................................................................51
Process Definition...................................................................................................................54
Process completion checklist..................................................................................................55
Project Status Reporting...............................................................................................55
Policies....................................................................................................................................56
PMO Guidelines & Policies...........................................................................................56
Pipeline Phase........................................................................................................................57
Post-Pipeline Phase................................................................................................................57
Documents Policy.......................................................................................................59
Document templates Mapped to Phases................................................................................60
1
Chapter
Introduction
T
he project lifecycle describes the tasks that must be completed to
produce a product or service. Different project lifecycles exist for
specific products and services. (For example, the lifecycle followed to
build a house is very different from the lifecycle followed to develop a
software package.) The project management lifecycle defines how to manage
a project. It will always be the same, regardless of the project lifecycle being
employed.
Project tasks and project management tasks are concurrent and ongoing, and can
be associated by project management deliverables. The Project Schedule, for
example, contains both project and project management tasks. Phases in the two
lifecycles will overlap, depending upon the project lifecycle being employed. The
Project Manager needs to be aware of how the inputs and outputs of one lifecycle
affect and shape the other.
Project Initiation
Project Planning
Project Closeout
This guidebook will explain each of the above phases but before that it is important
to understand the basics of a Project Management Office (PMO).
1
2
Chapter
2
I S S P R O J E C T M A N A G E M E N T G U I D E B O O K
The criteria for Fast Track projects
adhere to any of the given below:
1 2
IMPORTANT!!!!
4
by the size, complexity and environmental
considerations of each project. The project
management team has the overall
responsibility for determining what is
ultimately appropriate for any given project,
which would be agreed to by the customer and
stakeholders. Project elements include the
following.
5
The PMO sometimes becomes a change agent
- identifying opportunities for change within the
organization, determining the best approaches,
and introducing the changes to the community.
One PMO task is to look outside the
organization and identify other companies'
ideas and best practices that can be applied.
The PMO can communicate new ways of
thinking, introduce new tools and processes,
refine evaluative metrics, and work to
constantly establish a new baseline of
performance.
6
Applications &
ISS interactions
The Project management office will play liaison
role between application and ISS towers. As a
part of its initiation process, the Project
Management Office assigns a PMO rep for all
projects request that it receive.
Project Type
7
Project Categorization
T
hroughout this Guidebook, reference is
made to specific project categorization
and roles that must be performed at
various times throughout the life of the project.
The following section provides an overview of
the Project categorization used by the ISS
Program Management Office. It also discusses
the various roles that are required on projects,
what the responsibilities are for each role.
8
Initiative) Merrill Lynch) process)
9
Project Roles and
Responsibilities
Project Team
The Project Team is a group that is responsible
for planning and executing the project. It
consists of a Project Manager and a variable
number of Project Team members, who are
brought in to deliver their tasks according to
the Project Schedule.
Project Manager
10
Team completes the project. The Project
Manager develops the Project Plan with the
team and manages the team’s performance
of project tasks. It is also the responsibility
of the Project Manager to secure
acceptance and approval of deliverables
from the Project Sponsor and Stakeholders.
11
Performing Organization / Team
Members
Performing
organization is the The Team Member
group whose may or
may not
employees are be from
most directly performin
involved in doing g
the work of the organizati
project. The Project on.
Team Members
are responsible for executing tasks and
producing deliverables as outlined in the
Project Plan and directed by the Project
Manager, at whatever level of effort or
participation has been defined for them. On
larger projects, some Project Team
members may serve as Team Leaders,
providing task and technical leadership.
Project Sponsor
The Project Sponsor is a manager
The Project Sponsor provides with demonstrable interest in the
support for the
outcome of the project and who is
Project Manager,
approves major responsible for securing spending
deliverables, and authority and resources for the
signs off on project. Ideally, the Project
approvals to Sponsor should be the highest-
proceed to each
ranking manager possible, in
succeeding project
phase. proportion to the project size and
scope. The Project Sponsor
initiates the Project Proposal process, champions the project in
the Performing Organization, and is the ultimate decision-maker
for the project. The Project Sponsor provides support for the
Project Manager, approves major deliverables, and signs off on
approvals to proceed to each succeeding project phase. The
Project Sponsor may elect to delegate any of the above
responsibilities to other personnel either on or outside the Project
Team.
12
Customer
Customers comprise the business units that identified the need
for the product or service the project will develop. Customers can
be at all levels of an organization, from Commissioner to entry-
level clerk. Since it is frequently not feasible for all the Customers
to be directly involved in the project, the following roles are
identified:
Consumers
13
Stakeholders
Internal Stakeholders include all the people that are in
any way affected by the new product or service within the
Performing Organization. This may include the Project
Team, the Performing Organization Management,
Customers, as well as Customer co-workers who will be
affected by the change in Customer work practices due to
the new product or service; Customer managers affected
by modified workflows or logistics; Customer
correspondents affected by the quantity or quality of newly
available information; and other similarly affected groups.
Vendors
Vendors are contracted to provide additional products or services
the project will require and may be members of the Project Team.
The membership is determined by the Project Sponsor and may consist of:
14
The Project Sponsor, who normally chairs the meetings;
The Customers;
15
3
Chapter
16
Pipeline Process Flow
No NO
Request Status :
Follow Apps SDLC Is it an
Approved Open Helpdesk PM gathers Process & PMO Yes Application
Approved Fast track Request
ticket or Service required Yes guidelines project ?
pending info ?
Rejected request information
Deferred
Pending Add 'l Info No
Cancelled by BU No
Final
END
Inform requestor & Follow PMO
Request Reviewed Request guidelines
The Review Board : This board update request
monthly
Yes
Deffered?
status
will have people representing all
avenues of TechCentral .
END
Follow Std.
Change Process
No
END
Yes
Rejected/
Cancelled by BU
Process Definition
Process Objectives
The objective of the pipeline process is to review all the project
requests submitted to the ISS PMO and identify valid project
requests to work on.
Begins When
A project request form is submitted to the PMO
Includes
Review project requests
Categorize projects
Excludes
Project Initiation/planning/execution
Ends
When a project request is approved or rejected.
RICAP Chart for Project Pipeline Process
Categorize request P
Initiation Phase
Once the project request is
Usually for ISS Projects, the
approved, a project manager is customer has
assigned. Further more for large already completed
projects, a budget or further the task of
management commitment is preparing a
required. The PMO might also reject business case. But
for a few Projects
a project proposal for many like the UK Data
reasons. A list of popular reasons is Centre Move, the
given below: business case as
well the proposal is
Project objective can prepared by the
ISS PMO.
be achieved by a project
in-progress
Define CSSQ
Define Project Budget
CSSQ : Cost Define High Level Schedule
Schedule Define High level Scope Project Budget
Scope Define Quality Objectives High Level
Quality Schedule
Scope Statement
Quality Parameters
Perform Risk Identification
Identify Risk
Document Risk
Process Objectives
Begins When
Includes (The list includes but is not limited to the following tasks)
Identify Risks
Document Risk
Excludes
Any detailed project planning activities.
Ends
C- Co-ordinate
RICAP Chart
Tasks Sponsor/Client Project Project PMO
Manager Team
Identify Project Sponsor A P C
Identify Initial Project
A P C/A
Team
Develop Project Charter I P I C
Conduct Project Kick-off
R P R C
Meeting
Define Project Scope I P C
Develop High-Level
R P I R
Schedule
Identify Quality Standards R P R
Identify Risks P I R
Document Risk P I R
Develop Communications
I P I R
Plan
Compile initial project
R P R R
plan
Prepare formal
P R
acceptance package
Gain Approval signature
A P R
from Sponsor
Phase Completion Checklist
The main measurement of success for Project Initiation is the
decision to proceed with – or to halt – the project. While in the
majority of cases, a well-executed Project Initiation leads to a
transition to Project Planning, in some cases the organization is
best served by deciding that the project should not continue.
Before the final sign-off, however, the Project Manager can assess
how successfully the project is proceeding through its processes
by utilizing the measurement criteria outlined below. More than
one “No” answer indicates a serious risk to the continued success
of your project.
Questions Yes No
Do you have a committed and interested Project Sponsor attached to the project?
Did you verify that your Project Charter reflects the vision of the areas of the
Performing Organization affected by/involved in the project?
Did you identify specific benefits the product or service
developed by your project will bring to the Customer?
Has your Scope Statement been reviewed and accepted
by Customer Representatives who will benefit from
your project?
Has your Quality Management Plan been approved by
the member of your organization responsible for
quality assurance?
Did you review the impact your project costs will have
on upcoming fiscal year budgets with the Finance office?
Have your staff and materials acquisition plans been
reviewed with the Performing Organization who will be
paying for the staff and products being acquired?
Has the Project Sponsor reviewed your list of risks?
Do you have an approval form signed by your to Proceed to Project Sponsor
authorizing you to proceed to Next Phase Project Planning, or halting the project?
Have you provided sufficient information in your Initial project Plan to allow the Project
Sponsor to take the necessary action?
Planning Phase
The purpose of Project Planning is to define the exact parameters
of a project and ensure that all the pre-requisites for Project
Execution and Control are in place.
Process Objectives
Begins When
Quantify Risk
Excludes
Ends
Preliminary Budget
Establish Project Budget
Estimate
Perform Risk Risk Management
Assessment Identify New Risks, Update Existing
Worksheet
Risk Management
Quantify Risk
Worksheet
Risk Management
Develop Risk Management Plan
Worksheet
Refine Project Plan Establish Time/Cost Baselines Final project plan
C- Co-ordinate
RICAP Chart
Sponsor Project Project PMO
/Client Manage Team
Tasks r
Orient New Project Team
Members P
Review Outputs of Project
Initiation and Current Project
Status P P
Kick Off Project Planning P P C
Conduct Project Kick-off
Meeting R P P C
Refine Project Scope R P
Refine Project Schedule P P
Refine/Define Quality
Standards and Quality
Assurance Activities P P
Refine Project Budget P
Establish Project Budget R P R
Identify New Risks, Update
Existing R P
Quantify Risk R P
Develop Risk Management Plan R P
Establish Time/Cost Baselines P
Establish Procurement
Requirements R P
Develop Implementation Plan P I
Define Communications Plan P
Compile initial project plan P
Review Project Plan w/ Team R P R R
Gain Schedule and cost
commitment A C A C/I
Gain Schedule and cost
commitment from Stakeholder C C/I
Gain Approval signature from
Sponsor A P
Phase Completion Checklist
The ultimate measurement of success for Project Planning is the
successful Project Execution that follows, or a decision to stop the
project as, once again, the organization may be best served by
deciding that the project should not continue. Nevertheless, the
Project Manager can still assess how successfully the project is
proceeding by utilizing the measurement criteria outlined below
as it proceeds through Planning. More than one “No” answer
indicates a serious risk to the continued success of your project.
Questions Yes No
If not, have you obtained authorization to provide them with necessary and timely
training?
Have the supervisors of all resources assigned to tasks on your project agreed to
release those resources on the dates your project is expecting them?
Have you verified that the people responsible for signing off on scope changes and
deliverable approval forms actually have authority, and are willing, to approve the items
of expected magnitude and type?
Have the persons you identified as steering committee for issue/risk/change escalation
agreed to serve in that capacity?
Do you have an approval form signed by your Project Sponsor authorizing you to
proceed to Project Execution and Control, or halting the project?
Execution & Controlling
Phase
The project execution and the controlling phase is the longest
phase of the project management lifecycle, where most resources
are applied. Project Execution and Control utilizes all the plans,
schedules, procedures and templates that were prepared and
anticipated during prior phases.
Phase
Completion
Approval Project
Form Acceptanc
e Form
Process Definition
Process Objectives
Begins When
Excludes
Ends
C- Co-ordinate
RICAP Chart
Sponsor/ Project Project PMO
Tasks Client Manager Team
Orient New Project Team
Members Team P
Review Outputs of Project
Planning phase and provide
Project Status R P R
Kick Off Project Execution P C
Conduct Kick-off Meeting R P R C
Manage Project Scope P
Manage Project Schedule P
Implement Quality Standards P
Manage Project Budget P
Monitor New Risks, Update
Existing R P I R
Manage Scope Change I P I R
Monitor impact of scope
change on CSSQ R P I
Manage Time/Cost Baselines P
Manage Procurement
Requirements P
Execute Implementation Plan R P
Create Communications Plan R P I
Conduct Project Status
meetings P P P R
Execute Change Control
Tasks R P
Conduct Final status meeting R P R R
Gain Approval signature from
Sponsor A P
Phase Completion Checklist
The ultimate measurement of success for Project Planning is the
successful Project Execution that follows, or a decision to stop the
project as, once again, the organization may be best served by
deciding that the project should not continue. Nevertheless, the
Project Manager can still assess how successfully the project is
proceeding by utilizing the measurement criteria outlined below
as it proceeds through Planning. More than one “No” answer
indicates a serious risk to the continued success of your project.
Questions Yes No
Did you receive confirmation from ALL Project Team members that they agree with
their role descriptions, and that they understand and agree with the project objectives,
risks and timetables as recorded in the kick-off meeting notes?
Do your team members agree that the estimates to complete for all open tasks are
accurate?
Is the Project Sponsor aware of the latest total current budget for the project?
Were all changes to the scope, schedule, cost or quality parameters of the project
made with a signed scope change request?
Have all deliverables been presented to decision makers with prior preview of the
deliverable in progress?
Are all project issues recorded in the Issue Log in the Project Status Report?
Is the Status Meeting being held as often as indicated in the Communications Plan?
If any Customer Decision-Makers are consistently absent from the status meetings,
have they designated a replacement?
Do you have a Project Acceptance Form signed by your Project Sponsor accepting the
project?
Close-out Phase
Closeout begins when the user accepts the project deliverables
and the project sponsor or the customer concludes that the
project has met the goals established. The purpose of project
closeout is to assess the project and derive any lessons learned
and best practices to be applied to future projects. Project
Closeout contains the following high level tasks:
Turnover to Operations
Administrative Close-out
Turnover to Operation
The most important aspect of project The turnover &
closeout is the physical turnover of acceptance
control of the product, or service activities
delivered by the project. All project include but
are not limited
deliverables will need to be to knowledge
maintained and supported after the transfer,
project team disbands. An operational documentatio
unit of the organization (for which the n transfer,
deliverable is developed) assumes and physical
transfer of the
responsibility for the support of the deliverable.
deliverable.
Post-Implementation Review
The review starts with a survey designed to solicit feedback on
the project from the Project Team, Customers, Consumers and
other stakeholders. This survey is available on the project
SharePoint site to all the team members.
Administrative Closeout
Project Closeout ends with administrative closeout. The
administrative close-out involves completing a signed Project
Close-Out Form which has to be approved by the project Sponsor.
Project team also collaboratively documents the lessons learned
during the project.
Lessons Learned
Manage CSSQ
Manage Project Budget Conduct post implementation
Manage Project Schedule review
Manage Project Scope
Project
Implement Project Quality Conduct Project Performance Survey
Infomration
Assess results of survey
Document Lessons learned
Monitor & Control Risk Sharepoint
Survey
Monitor Risk Result
Control Risk
Monitor Impact on CSSQ
Perform Administrative Close out
Complete Project Close -out Form
Document lessons learned
Manage Project Plan Archive Project Information Signed
Manage Time/Cost Baselines Project
Manage Purchase Requirments Close-out
Manage Implementation Plan Form
Manage Testing Plan
Conduct Status Meetings
Manage Change Control Tasks
Manage Transition Plan All Project
Manage Communications Plan Docs
Project
Acceptanc
e Form
Process Definition
Process Objectives
Begins When
Excludes
Ends
Lessons Learned
Document Lessons learned
Document
Archive information in
Archive Project Information
server
RICAP Chart
C- Co-ordinate
RICAP Chart
Sponsor/ Project Project PMO
Tasks Client Manager Team
Identify Production support
team P
Complete turnover activities R R P
Conduct Project Performance
survey R P P R
Assess survey results P
Complete Project Close-out
Form A P
Document Lessons learned P P P R
Archive Project Information P
4
Chapter
Questions Yes No
Were best practices and lessons learned appropriately identified and documented in
such a way as to facilitate their application to all types of projects?
Scope Management
Introduction
A scope change is where a request is considered to change the
agreed scope and objectives of the project to accommodate a
need not originally defined to be part of the project.
Priority
There are different priority levels for change requests, based on
their impact to the project. The following are the priority levels by
the PMO.
Impact
The effort required to implement a given change request is not
constant throughout the project. As the project progresses
towards implementation, its ability to absorb scope changes
decreases and the likelihood of cost and/or schedule impact
increases. For example, it is more difficult to accept and
implement a functional change during testing than it is to accept
and implement the same change during design.
Depending on the phase of the project, a change in scope can
potentially impact the project schedule, cost, and risk. Hence, a
change can even change the project categorization and a small 2-
day work might turn into a big project.
Determine impact
Determine
on cost , time ,
Scope change Does it impact cost , alternatives to
Valid Request ? Yes effort, risk & Yes
initiated time,effort ? accommodate
inform project
change
sponsor
NO No
Continue project
Scope change as planned &
request not implement scope
pursued change
No
Scope change is
not pursued
Scope change for standard & complex work
A major difference in a scope change process for complex work
compared to small work is the requirement of a Scope Change
Request Form. A potential scope change requests can be filed
by any project stakeholders, including the project team, clients,
sponsors, etc. The scope change can be surfaced through verbal
or written means, but it will be formally documented using a
Scope Change Request Form.
Yes
Yes
Update project
Perform
plan to include this
investigation
work
No
Scope change is No
not pursued
No change to
Close scope
project schedule
change request
or cost
Process Definition
Process Objectives
Begins When
Excludes
Ends
Questions Yes No
Are all scope changes being registered in the scope change log?
Has the sponsor or the customer decision-maker approved all the scope changes
included in the project plan?
Is the project plan changed and baselined after each scope change?
Apart from the weekly project status meeting that might take
place within the project team and the performing organization,
the PMO has certain guidelines for status reporting using the MS
Project Server 2003.
The PMO has built a few views like the Project Health Scorecard
view which provide the senior management a quick view to
status of all the projects within TechCentral. The PMO has also
created a view called the TechCentral Project Review Meeting on
the Project Server which is used for Monthly Project Review
Meeting with the CIO. All project presentations during this
meeting are required to be in a specific PowerPoint format. The
template for this PowerPoint slide is available in the Templates
and Forms folder under documents section of the PMO Website.
Please contact the PMO rep for instructions on updating the
project status in the Project Server.
Policies
It is the responsibility of the project manager to update
the project status and also ensure that the current status of
the project reflects on the project server.
Pipeline Phase
A Project Request Form has to be submitted to the
PMO to initiate any sort of project.
Post-Pipeline Phase
All complex projects must have a project charter
which has been approved by the project sponsor.
=Optional = Required
Document templates Mapped to Phases
Executing
Executing&&
Initiation
InitiationPhase
Phase Planning
PlanningPhase
Phase Closeout
Closeoutphase
phase
Controlling
Controlling
Scope Change
Form