3
Introduction• Terminology
– Implementation, Transition, Handover • Gating Certification Request For Change
(RFC) and Project Closure report.• Communication • Application Protection Team engaged by
Application Services.• Transition Agreement – early engagement.
4
Transition
4
SDLC: Overview
PHASE 5
SupportInitiate
PHASE 1
ConceptRFP
Analysis
PHASE 2
Plan CloseImplementExecuteDesign
PHASE 3
Plan
Hand-over
PHASE 4
AS/OPS Engagement
Transition Agreement
6
ImplementationProcess• Request for Change is the key.• What is a change?
– Not just used for hardware– Application Implementation– Application Go Live– Modifications to hardware / application
7
ImplementationProcess• Project Team responsible for implementation.• Project Manager completes the RFC and obtains
required approvals.– Application Services Manager, Operations Manager
and Client. • Delivery Manager approves Implementation /
“Go Live” with receipt of the RFC. • AD Change coordinator actions.
8
Implementation• What is required to implement a system? (draft)
– Request for Change with approvals– Delivery Manager approval– Approved Service Desk Support Guide– Source code hand-over– Chart of Authorities– Sanitization scripts– Updated Portfolio – active status– Other Draft Deliverables in circulation
9
TransitionProcess• To be negotiated during project planning.• AD does not have access to production.• Service Desk takes calls.• AD still responsible for support and provides
direct support to AS and OPS (novice drivers).• Finalize handover deliverables.
10
HandoverProcess• Project Closure report is key.• Includes all project deliverables.• Hand-over is incorporated into this deliverable.
11
Project Closure ReportApplication Services Acceptance
<< This section requires the signature of the Application Services Manager identified on the preceding Application Services Response to Project Notification document. >>
Manager of Application Services
(name) (signature) (date)
Comments: <<insert comments or additional information here if required>>.
Operations Acceptance
This section requires the signature of the Operations Manager(s) identified on the preceding Operations Response to Project Notification document. If the approval of more than one manager is required, copy the signature block as required.>>
Manager of Operations
(name) (signature) (date)
Comments: <<insert comments or additional information here if required>>.
12
Summary• Utilized existing processes.• Eliminated duplication (gating
certification).• Early engagement of AS and OPS.• Approvals are done by those ultimately
responsible – typically manager level.• Escalation is ok.• Quick Reference Guides.
13
Next Steps• Pilot Projects• Use the Request for Change for all
changes.• Use gating certification until told otherwise.