Journey Centric Delivery Day 1 Live Plan

Slides:



Advertisements
Similar presentations
Project Name Kelly Waters July Author: Date: Version:
Advertisements

Business System Options
Technical System Options
CONFIDENTIAL: Presented under NDA, do not redistribute EDU Windows EDU Proof of Concept (POC) Program Program Overview for Schools Partner Name Partner.
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
ESOS COMPLIANCE PROCESS 26 FEBRUARY REGULATORY APPROACH.
Release & Deployment ITIL Version 3
Understanding Information Systems. Information System (IS) An IS is a combination of people, hardware, software, computer networks, and data that organizations.
Information Systems Chapter 10 – Computers: Understanding Technology, 3 rd edition 1November 13, 2008.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
Chapter 6 Organizational Information Systems
Chapter 16 Structured Systems Analysis. Learning Objectives Know goals, plans, tasks, tools, & results of systems analysis Understand/appreciate costs.
INFO425: System Design INFORMATION X Chapter 8 Evaluating Alternatives for Requirements, Environment, and Implementation Evaluating Alternatives.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Chapter 5. Why is Planning Important Need to plan because: Investors, guide for owners and managers, direction and motivation for employees, provide an.
Response to an Emergency Training for 211 Staff in Ontario Updated September
A2 Agreement Trial ICT November Key Points from Moderation  Majority of centres applied the assessment criteria successfully  Tasks selected and.
We produce exceptional products in a highly-engaged environment that maintains continuous focus on our clients’ business needs and goals..
Slide 1 A Practical Guide to Issuing a Request for Proposals Notes.
Insert name of presentation on Master Slide The Quality Improvement Guide Insert Date here Presenter:
Presenter: Igna Visser Date: Wednesday, 18 March 2015
Leadership Development at Bruce Power
Rapid Launch Workshop ©CC BY-SA.
Office 365 Security Assessment Workshop
Partner Toolbox Cloud Infrastructure & Management
CallTower Implementation Process Overview
Work Package 11 Name David Giaretta Institution APA/STFC
Software Configuration Management
Instructional slide to Partner: REMOVE BEFORE PRESENTING TO CUSTOMER
Windows Azure Jump Start Service
Office 365 Fast Track Migration Service
Initiating systems development
Evaluating performance management
THE FEASIBILTY STUDY LECTURE-5.
Z26 Project Management The Effectiveness of Workshops Graham Collins University College London (UCL)
Chapter 3: The Project Management Process Groups: A Case Study
Guidelines for Successful Product Evaluations
Project Specification
Project Roles and Responsibilities
2. Question and Answers 2.1 Follow-up on Open Items
Marketing automation is a very active segment of the CRM software market. Not only are new vendors entering the market, but existing market leaders are.
Project Plan Template (Help text appears in cursive on slides and in the notes field)
Services Offers Luc Maufrais April 2017.
Guidance notes for Project Manager
Principles of Project Management Case Study - Programme Management: Developing a Blueprint Graham Collins University College London (UCL)
IS&T Project Reviews September 9, 2004.
Chapter 13: Systems Analysis and Design
The role and value of the pre-sales person in the sales cycle
Automating Profitable Growth™
System Review – The Forgotten Implementation Step
Systems Analysis and Design
Centre name Project Kick Off.
Project Management Process Groups
Data Migration Assessment Jump Start – Engagement Kickoff
About this Template Dear Colleague, This template is provided by Valooto to help you communicate the facts about your need for a CPQ (Configure Price Quote)
Employee engagement Delivery guide
DSC Governance Sub Group Recommendations
ISO 9001:2008 – Key Changes NOTE: use of this webinar depends on the instructor/speaker using the text in the notes of the slides!! Examples and speaking.
Preparing abstract submissions for the International Forum
Data Office POAP April/May 2019
Sales operations Project support overview Presenter's Name
Joint Application Development (JAD)
(Project) SIGN OFF PROCESS MONTH DAY, YEAR
Automating Profitable Growth
Planning the Prepare Stage
Executive Project Kickoff
Chapter 13: Project Stakeholder Management
Co-production: Enablement Tracking & Reporting
Executive Governance Template
Presentation transcript:

Journey Centric Delivery Day 1 Live Plan

Day 1 Live Plan – What is different for the business ? Customer Journey : Loan origination. Callers to our contact centre will be taken through a new fact- find which will recommend a loan product, and start the application for the product. Business benefits : Reduce time to apply for a loan by 20% by reducing re-keying. Record fact find against the Loan for regulatory reporting. Systems Change : stop using the current excel based fact find, which means we can prove responsible lending more easily in the future. Loan applications will be auto started from the fact find. Expected Users : 50 model office, ramping to 300 over 3 months as we train. Expected Customers : All existing customers who call to request a loan. NOT new customers in this phase. Data Migration : None. The current excel fact find will be archived, and future responsible lending reports will be done from the new system Future phases : Expand fact find process to capture the information to apply for the recommended loan product, so we can auto complete the loan in the current systems and “wrap and renew” – keep using the current systems with a faster, automated front end. Timescales : First go live 90 calendar days after the project kick-off. Subsequent go lives every 45-60 days. Training : 1 day onsite training for all staff just prior to go live. Four ops staff will work as developers to be able to maintain the system after go live. Software projects tend to focus on what the software is to do, rather than how the business will use it. This makes it hard for the business to understand who and what will be impacted at Go Live. This Day 1 Live Plan gives a simple summary of what will be different on the first day of live usage from the perspective of the business. As such, it does not focus on interfaces, or testing, or hardware, or functionality. It describes how the business will change and be affected. It is intended as all of : A aid during sales to describe how the business will be affected A statement of scope to be reviewed during every executive governance meeting, as the basis to decide if we are delivering on the goals A training tool to assist with the business change management goals A development tool, to guide sprint planning and development decisions Ultimately this forms the basis for the change management plan It is prepared by the Solution Consultant and Practice Leader during the sale, forms part of the proposal clinic, and is maintained and updated by the Engagement Leader or Practice Leader. This covers just the functionality for the next MLP to be delivered - not the entire project, and is typically used as part of the acceptance criteria.  

Insert Scotts slides here