FORM – PSR v2
Monthly Project Status Report
Project Name
Exchange 2010
Upgrade
IS Project Code
IS-0192
Project Manager
Alec Coleman
Project Sponsor
Gregor Waddell
Report Period From
1 Nov 2010
Report Period To
30 Nov 2010
RAG Status
Green
Report Number
1
Milestones (from draft PPD – still to be
confirmed)
Planned Date
(from PPD)
Produce an Architectural Design for
Exchange 2010 installation, including storage
levels required for the increased archiving
period, backup and recovery and
performance monitoring and tuning
procedures.
Jan 2011
Produce Architectural Design for Symantec
eVault and integration with Exchange 2010
Jan 2011
Build a working, supportable and
manageable pilot Exchange 2010
environment.
Feb/Mar 2011
Produce strategy for migration of Outlook
2010 Client.
Produce a strategy for migrating to Microsoft
Forefront Online Protection for Exchange
(FOPE).
Expected Date
Date Completed
Feb/Mar 2011
Feb/Mar 2011
Knowledge transfer/training of ISMS staff
Mar 2011
Provide guidance and light-touch training
regime for staff, integrating with OCS 2007
and Windows 7 rollouts.
Mar 2011
Complete Rollout and Training by
May 2011
End Project Activities
Jun 2011
Progress achieved this period

Exchange 2010 training booked as follows:
17th January – Richard Mainprize
10th January – Nigel, Tim, Ian and Simon
7th February - Rob
D:\612934628.doc
Page 1 of 4
Version 2: January 2008
FORM
v2.1
–
PSR

Produced and issued consultancy brief to suppliers

Received responses from suppliers

Draft Mandate produced (GW subsequently advised not needed as we would go straight to
PPD)

Draft PPD produced

Draft project plan produced

Project kick-off meeting held

Emailed Graham Howarth asking if he would be Senior User on the project

Asked HR to investigate a training needs analysis

Emails sent advising that orders will be issued to Blue source for the Evault upgrade and
Salford for the design of Exchange 2010

Planned workshop with Salford for 15/12
Outlook for next period




Place formal orders with Blue Source and Salford
Attend workshop with Salford and technical team on 15/12
Refine and agree PPD and Project plan
Obtain design from Salford
Key Risks
Potential Extent
of Impact
(H, M, L)
Likelihood of
Occurrence
(H, M, L)
Progress / Support Required
Incompatibilities between clients still
using Outlook 2003 and Exchange
2010/eVault 9 provision.
M
M
Plan the pilot (and later the rollout) very
carefully so as to avoid such issues.
Wide range of tests to scope the issues.
Disruption to service
transitions / migrations.
any
M
M
Plan the pilot (and later the rollout) very
carefully so as to avoid such issues.
Impairment of our DR position during
transitions / migrations
M
M
Plan the pilot (and later the rollout) very
carefully so as to avoid such issues.
Interruption to in / out flow of email
during transition.
M
H
Design a means of trialing new
provision first and building confidence
and knowledge transfer to Ops.
Impairment of anti-virus service during
transition (leading to risk of mass
infection etc).
M
H
Design a means of trialing new
provision first and building confidence
and knowledge transfer to Ops.
An extensive training plan will need to
be drawn up which, based on past
experience will take up the majority of
an administrators time for at least 3
months.
M
H
Plan for additional resource.
Rollout following user training needs to
be closely managed and failure to
achieve proper co-ordination will
M
M
Planning between training organiser
and
Ops
during rollout. Good
communications strategy needed.
during
D:\612934628.doc
Page 2 of 4
Version 2.1: October 2009
FORM
v2.1
–
PSR
impact staff perception
Network Capacity issues create
bottlenecks a performance problems
when rolling out OCS
M
H
OCS project to confirm that this is not
an issue.
We are using different consultancies
for the design of Exchange 2010 and
Evault which could result in an
inconsistent approach.
M
M
Manage the suppliers and ensure ISMS
technical team are aware of what both
suppliers have designed.
Key Project Issues
Priority
(H, M, L)
Progress / Support Required
The current project plan for the new Exchange
environment is for later implementation than the
expiry of Sophos Pure Message email scanning in
Exchange 2003 environment on 30/3/10.
H
Determine dependencies and
decide whether earlier
implementation of Exchange
2010 is possible. Alternatively
extend Sophos Pure Message
Change Requests
Status
Priority
(H ,M ,L)
Progress / Support Required
VARIANCE
RAG
REASON
Budget Variance
Amber
60K has been allowed for in the original budget. This is
insufficient for anything other than the basic design,
implementation of the Exchange environment and training
of ISMS staff. We expect to become clearer on this once
the design has been received from Salford.
Out of the budget we have spent £999 for Blue Source
consultancy on OCS and £6577 on Exchange 2010
training for ISMS Ops and A&D staff. Plus, after the
designs from Salford and Blue source we will have £43K
left.
Schedule Variance (time)
Resource Variance
Scope Variance
Green
Blue source consultants from Evault are not available
before mid-January.
Green
Resources have been requested and approved for
December.
Amber
Project Kick off meeting agreed that OCS 2007 client
deployment be included within project scope.
The kick-off meeting agreed that the project will
investigate a training needs analysis with HR for aspects
that are not in scope e.g. Office 2010, Windows 7. Details
of training needs are awaited from HR.
Quality Variance
Green
D:\612934628.doc
Page 3 of 4
Version 2.1: October 2009
FORM
v2.1
Stakeholder Issue
Green
Risk Level
Green
–
PSR
We are awaiting agreement from Graham Howarth as to
whether he is willing to be senior user.
D:\612934628.doc
Page 4 of 4
Version 2.1: October 2009