Module 9 - Implementation Overview Module 9 brings together modules 5 through 8 to develop an implementation plan. The Implementation Plan provides the how and when to deliver the specific solution to meet the business strategy. After this module you will be expected to be able to design the implementation of the solution. Module Objectives This module addresses the following objectives 1. Solution design a. Customer Journey b. Information Architecture c. Technology architecture 2. Work breakdowns a. Work package decomposition b. Sequencing of activities c. Timelines 3. Governance a. Cost / benefit b. Costs and budgets c. Stakeholders 4. Adoption and change management Module 4 framed an idea and using techniques in Module 3 determined it was feasible and viable. Module 4 documented the impact of the idea on the organisation from a business, information and technical perspective. Module 5 through 7 further developed the different perspectives. Module 8 outline different governance and methodologies which can be used to implement and govern solutions from the ideation phase through to post implementation. Module 9 draws on all the previous modules to develop an implementation plan outlining how to convert the conceptual plan in module 4 into a solution. Solution Design The solution design portion of the plan refers to further expanding the idea and communicating the workings of the idea to the audience. This is discussed in different levels of detail depending on the audience. The output from the Module 5 through 7 should be analyzed. Once analyzed and assessed the outputs can be reviewed holistically. This holistic review will identify gaps and impacts which will enable you to develop a comprehensive roadmap for the solution. Reading Selected Reading 9.1 The Open Group,2011, TOGAF Version 9.1., USA, http://pubs.opengroup.org/architecture/togaf9-doc/arch/index.html Read Chapter 13, 14, 27 and 28 TOGAF (2011) outlines how to transition from the planning phase of the solution to the implementation phase of the solution. The key to this is understanding the roadmap, the work to be completed, any milestones along the way and the plan to convert the idea to a physical solution. Roadmap The roadmap outlines the way to move from the current state to the future state. Customer Experience As outlined in Module 5 the customer experience is critical to the understanding of the solution that is needed to be developed. The implementation plan draws from the concepts in Module 5 and normally included the following information to support the customer experience: 1. Customer Journey – the channels, products and parts of the value chain the solution will support. 2. Personas – an outline of the type of people who will be using the solution 3. Human centered design – an overview / prototype of the solution and how it will interact with the different personas for the customer journey. Information Architecture The information architecture will outline the different 1. Application 2. Data 3. Integration This information can be overlaid onto the Customer Journey to show which application and data will support the different personas as they proceed through the customer journey. Technology architecture Like the information architecture this shows how the different technology will support the different personas as they proceed through the customer journey using the different applications and data. TOGAF (2011), section 13.4.3 outlines how the gap analysis can be performed across these different areas and provides some tools in presenting this information. Figure 1 : Consolidated gaps, solutions and dependencies matrix Source: TOGAF (2011) Work Packages From the different transition plans different work packages can be identified in order to transform the organisation from the current state to the target or future state. This could result in one of more projects which need to be performed in order to accomplish this. From this step resource requirements, project timings and capacity planning also need to be completed in order to understand the magnitude of the work. Assessing the risk of each of the projects is critical and providing mitigation plans if necessary to reduce the amount of risk. Using simple charts again information can be plotted to portray different information. For example. Project vs Resources, Project, Risk and Value etc. This provides the stakeholder with a very visual way to understand the different aspects of the project. Figure 2 : Project, Risk and Value Assessment Source: TOGAF (2011) Moving from the current state to the target / future state can require some interim milestones or transition architectures. As such these interim steps need to be identified and outlined on the roadmap. Additional tools like Gantt charts can be used to provide the sequencing of projects and activities to visually display the projects to develop the solution. Figure 3 : Cone of Uncertainty Source: McConnell, S (2006) Reading Selected Reading 9.2 McConnell, S,2006, The cone of uncertainty, USA, http://www.construx.com/Thought_Leadership/Books/The_Cone_of_Uncertainty/ Read the entire blog Estimating projects is complex. McConnell, S (2006) outlines when it is appropriate to commit to different estimates in order to gain a higher degree of accuracy. Governance Module 4 discussed cost benefit and risk and Module 8 discussed governance. As part of the plan a risk assessment is needed for each project to understand the different risks and risk mitigation strategies. A cost-benefit analysis needs to be completed to further refine the costs for the different resources needed to complete the projects. Adoption and Change Management One of the key determinations which is needed for is the type of development methodology which will be used to deliver the solution and the different stakeholders involved. This is key to understanding how quickly value will be delivered to the business. Reading Selected Reading 9.3 Varadaraj, M & Goud, N, 2012, Successful Software Adoption - A study of Software Implementation Methodologies, New York Read the entire article It is important to understand the findings in the article as this highlights some of the issues with the implementation of software in an organisation. Module Review Questions 1. In today’s technology environment which do you think is more challenging the implementation of technology or the change management within an organisation to adopt and use the technology? 2. From a software project implementation perspective which categories of costs would you expect in order to implement a solution? 3. What kind of pricing models are there to acquire software? How would these different models impact the organisation? 4. How would you estimate a solution which is highly complex and never been done within an organisation before? Hint. Look at Waterfall vs Agile in Module 8. Module Review Question Responses 1. In today’s technology environment which do you think is more challenging the implementation of technology or the change management within an organisation to adopt and use the technology? a. Technology implementations are normally the easier. Getting people to change and adapt is difficult. 2. From a software project implementation perspective which categories of costs would you expect in order to implement a solution? a. People i. Salaries and wages ii. Professional Services iii. Managed Services b. Technology i. Hardware ii. Infrastructure iii. Software c. Training d. Other i. Sundry items ii. Supplies iii. Team building 3. What kind of pricing models are there to acquire software? How would these different models impact the organisation? a. Perpetual b. Subscription 4. How would you estimate a solution which is highly complex and never been done within an organisation before? Hint. Look at Waterfall vs Agile in Module 8. a. Prototype and learn to gain an understanding then estimate Module Summary Module 9 has outlined how to develop an implementation plan and some of the contents which should be included. Note this is not at a detailed level and still considered a business document, as such a lot of detailed which is needed for when a solution is implemented will still be required. This additional detail is normally added as one progresses through the different projects for the specific solutions. The intent of this implementation plan is to inform business and the different stakeholders of the overarching migration plan needed to solve the vision outlined in Module 4. References King, J 2006, 'Demystifying Software Estimation', vol. 40, no. 21, p. 58 King, R 2011, 'Create a Portfolio Management Software Adoption Plan', Journal of Financial Planning, p. 24. McConnell, S, 2006, Cone of Uncertainty. Varadaraj, M & Goud, N 2012, 'Successful Software Adoption - A study of Software Implementation Methodologies', International Journal of Computer Applications, vol. 41, no. 16.