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.

The great collision of open source, cloud technologies, with agile, creative delivery

1,251 views

Published on

Published in: Marketing, Technology
  • Be the first to comment

The great collision of open source, cloud technologies, with agile, creative delivery

  1. 1. The great collision of open source, cloud technologies, with agile, creative delivery 11 July 2014
  2. 2. • First Woman in Science and Technology • International entrepreneur of the year 2013 • Digital Innovation award 2013
  3. 3. Some of our clients
  4. 4. What we will be covering • Scene setting • Beyond the digital tipping point – how cloud, agile delivery and open source is creating disruptive change • The lasting impact of the communication revolution
  5. 5. 1. Scene setting
  6. 6. Welcome to the revolution
  7. 7. The next phase of the digital communications revolution
  8. 8. A powerful global conversation has begun. Through the Internet, people are discovering and inventing new ways to share relevant knowledge with blinding speed. As a direct result, markets are getting smarter— and getting smarter faster than most companies The original browser
  9. 9. Internet and web a huge disruptive force for change The change challenge
  10. 10. Needs to be recognised that digital is a strategic competency, rather than just another tactical channel in the marketing mix The change challenge
  11. 11. Ignoring this subtle difference is critical The change challenge
  12. 12. The change isn’t going to slow down The change challenge
  13. 13. How do we cope with this? 1. We have to recognise we can’t plan for change 2. Need to embrace change as a constant factor 3. Don’t plan for change in your organisation, plan for your organisation to change The change challenge
  14. 14. Evolution of delivery methods to cope with change
  15. 15. Challenges facing today’s marketing managers • Do more with less • Budget • Resources • High expectations from both internal and external stake holders • Pitfall of investing in commercial off the shelf software and not much budget left for customisation / development.
  16. 16. Delivery models have to improve 1. Endless specification processes 2. Document to the finest point of detail 3. Big go-live with meteoric impact?
  17. 17. UK Gov’s Digital Service (GDS) is leading the way, trail blazing radical new approaches Radical change is not only necessary but also unavoidable.
  18. 18. 2. User-centric thinking
  19. 19. We need to mean it Our mouths are full of customers But our practice is often full of ourselves
  20. 20. 3. Embracing open source tools, cloud and agile business models
  21. 21. The fact that open source is free is great, but there is more to it than that Understand the background to open source beyond “free”
  22. 22. Open source built on change Understand the background to open source beyond “free”
  23. 23. Changing software wasn’t always easy Understand the background to open source beyond “free”
  24. 24. No scope to play, just use as intended Understand the background to open source beyond “free”
  25. 25. Geographically limited Understand the background to open source beyond “free”
  26. 26. Against all odds.... and conventional wisdom and economics Understand the background to open source beyond “free”
  27. 27. 60% of all web services run on open source Understand the background to open source beyond “free” Source: http://w3techs.com
  28. 28. Now there are huge communities changing & developing based on needs Understand the background to open source beyond “free”
  29. 29. So in a quickly changing world, community driven software can only be good Understand the background to open source beyond “free”
  30. 30. Forrester
  31. 31. Forrester
  32. 32. Security concerns around open source Understood the myths and reality surrounding open source security concerns. One theme we heard over and over again as we spoke with interviewees is that the security concerns for open source solutions aren’t that different from those faced when implementing proprietary solutions.
  33. 33. Technology is THE enabler! Yet too often it seems like a set of constraints to be worked- around, an obstacle to be overcome, or set aside.
  34. 34. Open source fits in to the change challenge
  35. 35. It’s no sliver bullet to these challenges, but it can help Where open source fits in to change challenge
  36. 36. There’s organisational agility and then there’s agile projects Where open source fits in to change challenge
  37. 37. Project agility – Change the way you run a project Where open source fits in to change challenge
  38. 38. 3. Why are we hearing about agile now?
  39. 39. Amount of data
  40. 40. Change is an increasing challenge Technology growth is now following an exponential growth curve, and it’s not slowing down! 1476 1832 1887 1920s 1960s 1990 2007 1997 2010 1992 1971/3 1986 1989 2000 1994 1995 2004
  41. 41. Agility is a survival mechanism
  42. 42. Competitive advantage is evolving http://forrester.typepad.com/groundswell/2011/06/welcome-to-the-age-of-the-customer-invest-accordingly.html Cultural and technological change is disrupting business environments at increasingly faster rates.
  43. 43. Welcome to the ‘age of agility’ Age of Agility Survival is increasingly dependent on the ability to strategically adapt and respond to changes in culture and the business environment.
  44. 44. 3. Isn’t agile impossible for large organisations?
  45. 45. Benefits of a waterfall process • Robust and applicable to almost all types of design and build projects • Clear sign-off points for client • Detailed timeline for each component/phase • Client review and iteration periods • Prototype phase allows client to see exactly what they are getting prior to build • Detailed documentation • Create happy clients
  46. 46. However... • …what if you have to build a website in just one week?
  47. 47. UK Gov’s Digital Service (GDS) is leading the way, trail blazing radical new approaches Radical change is not only necessary but also unavoidable.
  48. 48. Reading Room’s Agile Creative Technology • Based on Agile Project Methodology • iterative development • evolve through collaboration • Dedicated Reading Room/client team, co-located throughout the project duration • constant decision-making
  49. 49. PHASE 1 Concept phase Nav Spec Design PHASE 2 PHASE 3 CMS Functional Prototype & Testing PHASE 4 Reading Room ACT project process Develop HTML Design Deploy to live PHASE 5
  50. 50. Agile in action
  51. 51. Cabinet Office – Solutions Exchange Forum Key objective was to create an online forum tool to allow :SMEs to engage with the government, Give suppliers a quick, free of charge way to pitch innovative ideas to save money and improve public services. Requirements gathering meeting: 16th June Deadline for site launch: 27th June
  52. 52. Agile Creative Technology Methodology Phase 2 & 3 (Mon from 1030hrs - Thurs) Truly iterative process of Dev creating pages while UX and Designer created the user journeys and design Constant communication between all team members enabled continuous iterations throughout 1 -2 catch up session per day (no more than a couple of mins) Phase 4 (Friday) Bug fixing Phase 1 (First 90 mins) Brainstorm session to establish the pages required for the forum M/S/C/W
  53. 53. Use projects to discover, as well as to deliver something Where open source fits in to change challenge
  54. 54. “At my previous companies building a website would be like unveiling the new Taj Mahal, and then you had the next one two years later. Now you start in a caravan and upgrade it bit by bit and keep things moving forward, it’s a more iterative process.” Ryanair CMO Kenny Jacobs
  55. 55. So what’s holding us back?
  56. 56. Long-range planning (Over long-term strategy)
  57. 57. Big technology commitments Need a mocked up image, for a contract “Big clunky inflexible contract, monolithic systems ltd”
  58. 58. Resistance to change Need a mocked up image, for a contract “Big clunky inflexible contract, monolithic systems ltd”
  59. 59. Always one step behind the customer
  60. 60. And for the future
  61. 61. You ain’t seen nothin’ yet
  62. 62. IoT & M2M Opportunities
  63. 63. Signs CCTV Energy Signals HVAC Information Temperature Location Security Air quality Lighting Personal Directions Noise Fire & Emergency HumidityMaintenance Vibration Access Control Gas monitoring Telecomms Infrastructure Waste Mobile Comms Advertising Weight IoT & M2M Opportunities Travel profile
  64. 64. And lots and LOTS of data
  65. 65. Gamification http://www.youtube.com/watch?v=yr-kKEylrJ8&feature=related
  66. 66. Moving from research to an experimental approach Our understanding of the people formerly known as the audience needs become much more sophisticated.
  67. 67. Arduino and Raspberry Pi
  68. 68. Major companies like BT are taking these changes very seriously. Hiring analysts to understand how they need to adapt their services channels for hyper connected customers.
  69. 69. Change creates disruption and organisational agility becomes a necessity
  70. 70. Time to embrace a more ‘agile’ approach 5 Year Plan ‘Agile Iterative Strategy’ Proprietary technology Open Source & Cloud Based Technology Management Information Structure & hierarchy Flexible systems and processes Experimental, data-led, decision making
  71. 71. What does an agile organisation look like? Business Information / Big (or little) Data OperationsFinanceMarketing Agile Iterative Strategy Real-timeInsight Decisionmaking Communication & Collaboration Rapid Product, Platform, & Service Delivery AgileCulturalFramework EmpoweredPeopleandTeams Modular Open Source Cloud Technology
  72. 72. Architects of digital change
  73. 73. 2. Some definitions
  74. 74. Agile principles • 1. Customer satisfaction by rapid delivery of useful software 2. Welcome changing requirements, even late in development 3. Working software is delivered frequently (weeks rather than months) 4. Working software is the principal measure of progress 5. Sustainable development, able to maintain a constant pace 6. Close, daily cooperation between business people and developers 7. Face-to-face conversation is the best form of communication (co-location) 8. Projects are built around motivated individuals, who should be trusted 9. Continuous attention to technical excellence and good design 10. Simplicity—the art of maximizing the amount of work not done—is essential 11. Self-organising teams Customer satisfaction by rapid delivery of useful software Working software is delivered frequently 12. Regular adaptation to changing circumstances Working software is delivered frequently, and is the principle measure of progress
  75. 75. Cloud Cloud Computing Cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as autility (like the electricity grid) over a network (typically theInternet). 11/07/2014 86
  76. 76. The cloud
  77. 77. Open Source

×