1 DEPLOYMENT AND OPERATIONS MODULE 23 ECM SPECIALIST COURSE 1 Copyright AIIM.

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

SWE IG Meeting Paris, CRE XBID Overview Supported by.
Roadmap for Sourcing Decision Review Board (DRB)
Requirements Specification and Management
Course: e-Governance Project Lifecycle Day 1
Software Quality Assurance Plan
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
© Tally Solutions Pvt. Ltd. All Rights Reserved 1 Shoper 9 Implementation in Chain Store March 2010.
ITIL: Service Transition
DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Phase III – Validation Thomas Howard Chris Pierce.
PRJ270: Essentials of Rational Unified Process
Rational Unified Process
Software Project Transition Planning
SE 555 Software Requirements & Specification Requirements Validation.
Iterative development and The Unified process
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
IS&T Project Management: Project Management 101 June, 2006.
Remedy, a BMC Software company Change Management Maximize Speed and Minimize Risk in the Change Process.
Release & Deployment ITIL Version 3
IPM Methodology Overview and Fit Gap Prep. 8/17/2015 | 2 | ©2012 Ciber, Inc. Incremental Prototype Methodology IPM is a building block approach divided.
Load Test Planning Especially with HP LoadRunner >>>>>>>>>>>>>>>>>>>>>>
Effective Methods for Software and Systems Integration
Developing Enterprise Architecture
Web Development Process Description
S/W Project Management
PMP® Exam Preparation Course
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
Condor Technology Solutions, Inc. Grace RFTS Application Extension Phase.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Testing Lifecycle Practice
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
PPMT CE-408T Engr. Faisal ur Rehman CED N-W.F.P UET P.
Independent User Acceptance Test Process (IUAT)
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 © Quality House QUALITY HOUSE The best testing partner in Bulgaria.
Copyright 2014 Riverbed Inc. Confidential. 1 Kevin McGowan Principal Consultant September 10, 2015 Achieving Excellence in Managing the UC Lifecycle Riverbed.
MyFloridaMarketPlace CRB Meeting
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 6: Phase Management -Transition.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
RUP Deployment RUP Deployment Workflow
Rational Unified Process (RUP)
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
State of Georgia Release Management Training
Team-Based Development ISYS321 Managing the Information Systems Project.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
CHANGE READINESS ASSESSMENT Measuring stakeholder engagement and attitude to change.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
CHANGE MANAGEMENT - PART 2 MODULE 7
1 ECM APPLICATIONS AND SOLUTIONS - PART 1 MODULE 8 ECM SPECIALIST COURSE 1 Copyright AIIM.
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
SAP Methods Context PRM1_02.1 PwC Methods & Risk Management Lesson Objectives Participants will be able to: Understand how methods can mitigate project.
ITIL: Service Transition
ESTABLISHING A PROJECT PLAN MODULE 18
IEEE Std 1074: Standard for Software Lifecycle
Engineering Processes
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
Presentation transcript:

1 DEPLOYMENT AND OPERATIONS MODULE 23 ECM SPECIALIST COURSE 1 Copyright AIIM

ECM SPECIALIST COURSE Section 1: ECM Business Strategy Section 3: ECM Applications and Solutions Section 5: Foundations and Planning Section 6: Design, Deliver and Deploy Module 1: Introduction to ECM Program Delivery Modules 8 and 9: Applications and Solutions Parts 1 and 2 Modules 14, 15 and 16 Building a Foundation Parts 1, 2 and 3 Modules 20 and 21 Design Parts 1 and 2 Module 2: ECM Program Strategy Exam 3Module 17: Creating a Project Roadmap Module 22: Develop Module 23: Deployment and Operations Module 3: ECM Business Case Section 4: Business and Technology Assessments Module 18: Establishing a Project Plan Exam 1Module 24: Continuous Improvement Section 2: Change Management and Governance Modules 10 and 11 Business Assessment Parts 1 and 2 Module 19: Client Engagement Modules 4 and 5: Governance Parts 1 and 2 Modules 12 and 13 Technical Assessment Parts 1 and 2 Modules 6 and 7: Change Management Parts 1 and 2 Exam 2Exam 4Exam 5Exam 6 2

 Deliver/deploy activities - “Phase 5”  Production deployment tasks  Evaluation and launch  User and production acceptance testing  Pre-launch steps  Fallback planning  Transition support and monitoring  Module recap Copyright AIIM 3 AGENDA

Copyright AIIM 4  Deliver and Deploy  Operate  “Phase 5” PHASE 5 OF THE IMPLEMENTATION LIFECYCLE

 Post-pilot and/or model office work, the ECM environment finally reaches a deployment-ready state  Final steps for deployment involve finalizing how the solution will be deployed technically for production use  Key Tasks: ◦ Define deployment and installation method ◦ Deploy baseline production environment ◦ Deploy software to production Copyright AIIM 5 PRODUCTION DEPLOYMENT

 From the end-user standpoint ◦ User-facing ECM installations often use web-based interfaces ◦ May still be plug-ins or “fat clients” that are necessary to accomplish deeper integration into daily work tools and devices  From the server-side standpoint ◦ Align the full-blown delivery environment, with the identified tools, technologies and processes needed for final user and performance testing, and launch Copyright AIIM 6 DEFINE DEPLOYMENT AND INSTALLATION APPROACHES

 The production environment must be prepared and configured as defined by the technical architecture ◦ Time spent will vary greatly if a production or full test/staging- environment already exists  Key tasks include: ◦ Build IT environments ◦ Implement server(s) and client(s) ◦ Integrate into line of business applications ◦ Perform any customization or configurations Copyright AIIM 7 DEFINE BASELINE DEPLOYMENT

Copyright AIIM 8  Final deployment testing ◦ Ensure user acceptance tests (UAT) have verified system works without major issues  Final production verification tests (PVT)  Tests system from operational perspective ◦ System is fully functional and works under expected user load  Do not proceed to final testing stage if UAT fails ◦ Such as level 1 or 2 severity issues PRODUCT VERIFICATION

Copyright AIIM 9 1. Verify that previous UATs passed with no severity level 1 or 2 issues 2. Verify that 100% of relevant requirements for this iteration (or final system) were tested in pre- production environment 3. Sign-off on user interfaces and integration points after functional testing 4. Log any issues that are surfaced for production support resolution, or resolution before launch PRODUCT VERIFICATION - TASKS

 Analyze production support and issue log  Develop scenarios under which total or partial back- out may be required  Agree most likely scenarios with key stakeholders  Develop contingency plans for most likely scenarios  Review contingency plans with key stakeholders  Produce a ‘fallback plan’ for most likely scenarios and contingency plans Copyright AIIM 10 FALLBACK PLANNING

1. Verify that rollout processes and standards are in place for end-users, including: ◦ End user support ◦ Contingency operations ◦ Outage plans ◦ Deployment checklist 2. Verify that the delivery components are prepped for the operational environment: ◦ Operations tools and facilities ◦ End user tools ◦ Databases and/or repositories ◦ Control processes ◦ Operations support Copyright AIIM 11 DEPLOYMENT CHECKLIST

 Post technical deployment is the final evaluation, scheduled launch and post-launch verification and support  Transfers operations and support from the development/project team to operations personnel for solution moving forward  Contingency plans for any issues in final testing and launch should be in place and ready to activate, should any severe issues be identified  Validates that system is truly ready for rollout Copyright AIIM 12 EVALUATION

 Awareness and Communication ◦ Communicate reasons for change ◦ Use all available channels to communicate ◦ Communicate early and often ◦ Be aware of culture and politics  Communicate to all Stakeholders ◦ End-users who will be using the system ◦ Operations staff who will be running the system  Support for the technology  Support for the processes  Service level agreements (SLAs) Copyright AIIM 13 PRE-LAUNCH TASKS

 Development of content management awareness across the organization that supplements previous communication efforts  Ensuring take-up and effective use of relevant elements of ECM by all users as they are implemented  Keeping an eye on possible extensions to the scope of ECM  Assessing new developments which create content Copyright AIIM 14 LAUNCH TASKS

 No system has really been tested until it has been used in production  Project team, particularly technical specialists, need to be on hand to ensure that the system performs as expected in the production environment  Focus on the technical performance of the system as it transitions from pre-deployment to live Copyright AIIM 15 SUPPORT TRANSITION

1. Monitor and fine-tune new system through post- launch period to meet business requirements 2. Evaluate performance to ensure SLAs are met 3. Develop recommendations to reconcile any issues found, prioritize, and implement fixes 4. Ensure that transition from deployment staff to operations staff has occurred smoothly Copyright AIIM 16 PRODUCT MONITORING TASKS

 What is the actual measure of the following? ◦ Time to save and retrieve content with a mobile device ◦ Performance and reliability of system ◦ Completeness and integrity of content ◦ Consistency of content indexing ◦ User confidence / contentment with procedures ◦ Subject and frequency of support requested from users  Is support effort required as expected or is level much higher/lower? Copyright AIIM 17 POTENTIAL ACCEPTANCE CRITERIA

Copyright AIIM 18 MODULE RECAP  Deliver/deploy activities - “Phase 5”  Production deployment tasks  Evaluation and launch  User and production acceptance testing  Pre-launch steps  Fallback planning  Transition support and monitoring