Project Mercury

1
Project Mercury
PROJECT
MERCURY

• Steady State Governance
• Change Process

How changes to the Intranet Site (post go-live)
are processed (both before and after the end of
the project)
2
Guidance Notes

• Steady State defined
• Ideally, the Project will be phased in such a way
  that a single big bang release is avoided.
• As such, the portal will be live prior to the end
  of the project and thus be in steady state
  support mode at the same time as further project
  releases to the portal take place
• Once the project is over, only the steady state
  process will remain (and will need to cater into
  the future for ongoing changes to the intranet
  portal)
• Process Maps
• Four sets of process maps are included
• Prior to first go-live release
• Post go-live, but prior to end of the project
• After the end of the project
• Project Change process (see also change control
  chapter)

3

• Prior to first
• go-live release

At this point, the support team for the new
intranet portal is unlikely to be in place or
available for change works. There may still be a
legacy site team in place
4
Change Initiation
Software providers Service Packs and Security
Patches
Hardware providers Service Packs and Security
Patches
New Change Logged with Support Team and CR Form
Raised
SS Change Log (each change given unique ref no.)
Community Owners New site requests or changes to
legacy intranet sites
Rapid Estimate Report (given to change initiator)
Rapid Estimate Initial view on scale of effort
required to process the change
Further Info Request
Immediate Rejection (i.e Change clearly not
viable)
5
Change Assessment
Sponsorship Ensure there is a senior sponsor for
the change (named)
no sponsor
Senior Sign off of the CR Form
no funding
Funding Confirm that there is sufficient funding
to cover the estimate
Senior Sign off of Rapid Estimate
Rejection (i.e Change not approved)
small change
project change
larger change
For example Where the change is enterprise-wide
in nature, it may be appropritae to change the
main project scope
6
Larger Change Process
Project Management Plan
Project Initiation Initiate a new project under
the Intranet Programme
Statement of Requirements Project Plan
RFI / FRP sent to preferred suppliers
Resourcing RFP to select supplier and/or
mobilisation of internal resource
Project Execution Project Planning, development
and testing
Various Project Documentation Outputs
Release Implementation to the Live environment
in first release (if poss.)
Revised Site Documentation
End
End
7

• Post go-live, but prior to end of the project

At this point, the support team is in place and
is available for change works. All development
of legacy sites has been frozen out, whilst the
old sites are migrated
8
Change Initiation
Software providers Service Packs and Security
Patches
Hardware providers Service Packs and Security
Patches
New Change Logged with Support Team and CR Form
Raised
SS Change Log (each change given unique ref no.)
Community Owners New site requests or changes to
legacy intranet sites
Rapid Estimate Report (given to change initiator)
Central Team Changes to primary navigation,
tweaks and other changes
Rapid Estimate Initial view on scale of effort
required to process the change
Further Info Request
Immediate Rejection (i.e Change clearly not
viable)
9
Change Assessment
Sponsorship Ensure there is a senior sponsor for
the change (named)
no sponsor
Senior Sign off of the CR Form
no funding
Funding Confirm that there is sufficient funding
to cover the estimate
Senior Sign off of Rapid Estimate
Rejection (i.e Change not approved)
small change
project change
larger change
For example Where the change is enterprise-wide
in nature, it may be appropritae to change the
main project scope
10
Small Change Process
Revised Work Package Notes
Schedule Add the change to an appropriate work
package for SS team
Allocate change to developer or team
Storyboarding of pages other outputs
JAD Rapid and joint development and testing
Variation to any SLAs / Support Contracts
Release Implementation to Live at next available
project release
Revised Site Documentation
End
11
Larger Change Process
Project Management Plan
Project Initiation Initiate a new project under
the Intranet Programme
Statement of Requirements Project Plan
RFI / FRP sent to preferred suppliers
Resourcing RFP to select supplier and/or
mobilisation of internal resource
Project Execution Project Planning, development
and testing
Various Project Documentation Outputs
Release Implementation to the Live at next
available project release
Revised Site Documentation
End
End
12

• After the end of the project

At this point, the support team is in place but
the project team has been disbanded. Legacy
sites have most likely been decommissioned (or at
the very least disconnected)
13
Change Initiation
Software providers Service Packs and Security
Patches
Hardware providers Service Packs and Security
Patches
New Change Logged with Support Team and CR Form
Raised
SS Change Log (each change given unique ref no.)
Community Owners New site requests or changes to
legacy intranet sites
Rapid Estimate Report (given to change initiator)
Central Team Changes to primary navigation,
tweaks and other changes
Rapid Estimate Initial view on scale of effort
required to process the change
Further Info Request
Immediate Rejection (i.e Change clearly not
viable)
14
Change Assessment
Sponsorship Ensure there is a senior sponsor for
the change (named)
no sponsor
Senior Sign off of the CR Form
no funding
Funding Confirm that there is sufficient funding
to cover the estimate
Senior Sign off of Rapid Estimate
Rejection (i.e Change not approved)
small change
larger change
Agree Approach Depends on the size and nature of
the change
15
Small Change Process
Revised Work Package Notes
Schedule Add the change to an appropriate work
package for SS team
Allocate change to developer or team
Storyboarding of pages other outputs
JAD Rapid and joint development and testing
Variation to any SLAs / Support Contracts
Revised Site Documentation
End
16
Larger Change Process
Project Management Plan
Project Initiation Initiate a new project under
the Intranet Programme
Statement of Requirements Project Plan
RFI / FRP sent to preferred suppliers
Resourcing RFP to select supplier and/or
mobilisation of internal resource
Project Execution Project Planning, development
and testing
Various Project Documentation Outputs
Release Implementation to the Live environment
Revised Site Documentation
End
End
17

• Project Change Process

This is the process which should be followed if
the main project is still in progress and the
approach has been taken to progress the change
request through an addition to the (main) project
scope
18
Change Initiation
New Change Logged with Project Office and Cover
Sheet Raised
Change Request Log (each change given unique ref
no.)
Impact Assessment Report
Impact Assessment Effect on timescales, costs,
benefits and risk assessed by team
Further Info Request
Immediate Rejection (i.e Change clearly not
viable)
19
Change Assessment
Sponsorship Identify Project Board member who
will sponsor the Change
Invitations sent to Proposer
Further Info Request Decision taken to seek
further impact analysis prior to firm decision
Preparing the Case Sponsor prepares the case to
be made to the Change Board
Presentation of the Change Case
Change Board Minutes
defer
reject
accept
Rejection (i.e Change not approved)
20
Change Processing
Revised Project Management Plan
Reconfiguration Changes to Project Scope are made
Work Contracts with Suppliers amended
Revised Project Plan issued
Re-baselining Project Plan and Financial
forecasts are updated
Revised Financial Forecast
Revised Change Log
End