Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Migration approachquestionnaire checklist

664 views

Published on

Want to migrate from one technology platform to another?
Seems simple. Done so many times, this initiative still sounds like a deja vu to lot of teams and executives in organizations big and small, flat or hierarchical or matrix management culture.

First principle - Socialize, engage, educate, evangelize and get the buy in of direct and in-direct stakeholders.

How do you go through all that using a disciplined approach?

Check this out. Feel free to contact me for clarifications anytime via info @ ValueRealizationInc.com

Published in: Technology
  • Folks, if you find this document useful, I would appreciate a 1-line recommendation or simply Like on this page. Thank you
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Migration approachquestionnaire checklist

  1. 1. Copyright © 2013 Value Realization Inc. Migration Approach Questionnaire / Checklist Prepared for a large big data systems integrator.
  2. 2. Copyright © 2013 by Value Realization Inc. Article I. Introduction Migration of information technology components and processes should be preceded by a “discovery phase”. The output or result of this discovery phase is a document that typically captures known facts and unknowns, but also solicits a fair idea on perceived limitations or future expectations of state stakeholders of the current state. This result document should represent a” living / working state document”. This tool therefore is a critical input for subsequent high-level phases in the migration approach, namely, Discovery phase, Envisioning phase, Program commencement, and Final Migration Results. Article II. Intended Audience Stakeholders representing the current state as well as future state including members of IT teams, Business teams, business drivers, IT drivers and program sponsors. Article III. Document Maintenance and Use Guidelines  This document solicits information from across stakeholder groups.  This document should be collaboratively and progressively updated.  Expect responses to be progressively available and validated.  If response is not known, state so, so progressive discovery exercises can be undertaken.  Each draft release* should be maintained as a separate dated version for tracking.  Additional discovery / fact check questions can be incorporated.  Multiple conflicting responses should be flagged and resolved.  Attach Addition sheets if required to the questionnaire.  A copy of this sheet can be handed to as many appropriate respondents as required.  Copies received from respondents should be reviewed and verified for Consistency and Accuracy in responses to sections B and C.  If there is any inconsistency in responses to sections B and C, they should be reconciled and resolved.  Multiple respondent copies can be merged as one draft release*  Progressive updates will result in subsequent version of the release.  Questionnaire responses will be used to construct the checklist for Migration Program.  All checklist items should reflect in Project WBS.
  3. 3. Copyright © 2013 Value Realization Inc. A. Management (to be filled by business users, drivers and sponsors) 1. List one or more limitations, perceived or otherwise of the Current State, that you would like to see improved or incorporated in the Future State. Few options are listed for reference. ☐Performance ☐Business capabilities ☐Scalability ☐User Interactions+ ☐Others (please list) ☐Governance ☐ Data Accuracy ☐Integration with Other Systems ☐ Increased Visibility* ☐Service Levels ☐Others (please list) + The technology ecosystem user friendliness including getting timely, appropriate information and initiating workflows if applicable and as appropriate. * Visibility per Segregation of Duties (SOD) into Data, Audit, Authorization, workflows etc. <Provide additional insight to each selection above, is applicable, in this section below. Attach additional pages, if required, for this Q> 2. List one or more expected / desired outcomes from the Future State. ☐Performance ☐Business capabilities ☐Scalability ☐User Interactions+ ☐Others (please list) ☐Governance ☐ Data Accuracy ☐Integration with Other Systems ☐ Increased Visibility* ☐Service Levels ☐Others (please list) + The technology ecosystem user friendliness including getting timely, appropriate information and initiating workflows if applicable and as appropriate. * Visibility per Segregation of Duties (SOD) into Data, Audit, Authorization, workflows etc. <Provide additional insight to each selection above, is applicable, in this section below. Attach additional pages, if required, for this Q> 3. List one or more tools you are currently using in the context of current state. ☐Spreadsheet + ☐Reporting Tools* ☐Others (please list) + Spreadsheets linked to Databases. * List all reporting tools you are using. <Provide additional insight to each selection above, is applicable, in this section below. Attach additional pages, if required, for this Q>
  4. 4. Copyright © 2013 Value Realization Inc. B. Technology (to-be-filled by technical teams) * All information in sheets below requested strictly within the Scope of Current State. * Assumed that Current State “Scope” is broadly defined. Example: “Oracle CRM migration”. I. Infrastructure 1. List all Servers and related information in a spreadsheet table format. a. Server names b. IP Addresses c. Detailed Server Configurations including versions, disk capacities etc. d. Security configurations including DMZ ports configurations, use etc. e. Operating Systems installed including versions etc. f. Databases installed including versions etc. g. Other software e.g. COTS packages, ETL software, Drivers etc. h. Identify Dependency points. Examples include: Any installed component directly dependent on any components outside the Current State Scope /other systems etc. or vice-versa. i. List of Server Logins (and users), authorization levels and user categorization (if any). 2. List all vendors and support teams for each software/infrastructure component above. 3. List all SLAs, vendor contracts and Application category associated with above installed base. Examples of Application category include, COTS, legacy, homegrown, Cloud Vendor-hosted, Private Cloud, Open Source, Licensed etc. 4. List other applicable external dependent capabilities, SLA/contracts and policies Example: BCP, DR, Security Policies, Data Retention Policies. II. Software Configurations 1. List all Applications (Business Application names) and for each Business Application provide a. Database(s), Database Server and IP(s) b. Web Server(s), Middleware, and Reporting Server(s) etc. c. Physical Architecture Specifications for each Server above. d. Server Repository (if any) architecture, configuration specifications. Example: Reporting Server repository and custom configurations. e. Schemas and documentation describing use and dependencies. f. Database Users, purpose of access granted to user, whether Active or Dormant. g. Roles and Privileges h. List All sources of Data for the Respective Application(s) i. List all Subscribers for the Respective Application(s) j. Database Sizing, Planned and Actuals, both. Compute Annual Growth Rate if possible. k. List All Access Points including ODBC Connections, Reporting Applications, R/W Applications to each database.
  5. 5. Copyright © 2013 Value Realization Inc. III. Software Architecture and Design 1. Identify, validate and audit documentation for: a. Business Rules / functions implemented in the Current state Software System(s) b. Data Model(s) c. Physical Database Designs d. Business Data dictionary with appropriate names data types, widths and descriptions e. Meta data f. Data publisher/ Subscriber data mappings, business integration rules, data integration rules and ETL mappings. g. Software used in conjunction of Current State Software Application(s). Examples: Productivity software (SQL Navigator), SQL Loader, Java APIs etc. h. Enhancements or Defect fixes, not available in other software documents like architecture specifications, design specifications etc. i. User requirements, change requests, high Level software architecture, design document for the Current State System(s)/ Application(s) j. Software Development Environments (Production, QA, Dev etc.) along with Server name(s), IP(s). k. Business function components/objects e.g. pre-defined reports, encapsulated data components/objects, web services, customer developed APIs etc. C. Process 1. Identify, validate and audit processes and process owners, teams built around the Current State Application(s)/System(s) a. Change Control b. Release Management c. Production support (infrastructure, software listed separately) d. User training e. Levels of Support (examples include L1, L2 L3 etc.) f. Audit Control g. Business and IT Governance, Risk and Compliance Processes, Tools leveraged, documentation practices. h. Access Authorization protocols, Segregation of Duties (SOD) policies, appropriate audit rules etc. i. Current State Software Development Methodology. j. Current State Project Management Methodology. C. People 1. Identify, verify and document stakeholders and stakeholder RASCI for each technology component, processes above. 2. Create a High Level People, Technology, and Process Intersection Matrix.

×