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.

What is Rapid Innovation

2,842 views

Published on

Presentation given to JISC Innovation Group on 22 July 2010.

Published in: Technology
  • Be the first to comment

What is Rapid Innovation

  1. 2. <ul><li>Part 1.) ... support RI as an effective strategic innovation methodology. </li></ul><ul><li>Part 2.) ...utilise RI as a method for running programmes of work in your team. </li></ul><ul><li>Part 3.) ...think about the possibility of a cross-innovation group RI call. </li></ul>
  2. 3. <ul><li>“ If you think you understand JISC after a year of being here, you don’t understand JISC.” </li></ul><ul><li>-Malcolm Reed – </li></ul>
  3. 4. <ul><li>A programme is a collection of projects . </li></ul><ul><li>Programme Management is the overall concern for the value that projects collectively achieve as a programme . </li></ul><ul><li>“ Agile” is a project-based-methodology </li></ul><ul><li>“ Rapid Innovation” is a programme-based-methodology that embraces projects using “agile” techniques [1]. </li></ul><ul><li>“ methodology” is used as a *framework* here, NOT as a prescriptive instructional process. </li></ul>
  4. 5. Part 1 (Top Down) – The Strategic Significance of Rapid Innovation
  5. 6. DEGREE OF CHANGE in Technology / Software DEGREE OF CHANGE in Practice / Process 2 1 4 3
  6. 7. % of CHANGE in Technology / Software % of CHANGE in Practice / Processes 2 1 3 Project Outputs: a.) YES process changed b.) YES tools changed 4 Programme
  7. 8. % of CHANGE in Technology / Software % of CHANGE in Practice / Processes 2 1 4 3 Project Output: a.) Use of a new process within a community Project Output: a.) Use of a new technology in a community Programme
  8. 9. % of CHANGE in Technology / Software % of CHANGE in Practice / Processes 2 1 4 3 Project Output: a.) Develop and use a new technology i.e. jiscRI, vreRI, distribVLE, fsdRI, etc. Programme
  9. 10. <ul><li>The numbers: </li></ul><ul><li>39 Projects Funded >£40K per project </li></ul><ul><li>£1.5 million total </li></ul><ul><li>120+ Ppl received funding </li></ul><ul><li>13 high quality prototype tools produced </li></ul><ul><li>4 projects received further funding based on project output </li></ul><ul><li>Outcomes: </li></ul><ul><li>Visionary tools informing the sector of next set of new tech. </li></ul><ul><li>New developer skills injected into .ac.uk (mob, geo, LD, blog, JS) </li></ul><ul><li>Established community of developers as innovation stakeholders </li></ul>
  10. 11. Part 2 (Bottom-up) - Pragmatics of Implementing an RI Programme
  11. 12. <ul><li>Individuals and interaction, </li></ul><ul><li>over policies and technology. </li></ul><ul><li>Delivery of outputs (products), </li></ul><ul><li>over comprehensive documentation. </li></ul><ul><li>End user collaboration, </li></ul><ul><li>over stakeholder meetings. </li></ul><ul><li>Responding to change, </li></ul><ul><li>over following a plan. </li></ul><ul><li>*= That is, while there is value in the smaller items, RI values the larger items more. </li></ul>
  12. 13. <ul><li>Responding to change </li></ul><ul><ul><li>Provide structures that enable projects to change their plans : shared spreadsheet on project contact details , project plans in blogs, updates via twitter , power to update you , power to dictate how they should write documentation ... </li></ul></ul><ul><li>End User Collaboration </li></ul><ul><ul><li>Make sure projects engage end users: write it into Calls, do a project site visit to meet users, have them list users as part of the project, ask their users what they think... </li></ul></ul><ul><li>Delivery of outputs (products) </li></ul><ul><ul><li>Know what they are selling: know the single thing that projects are going to produce and to who (the audience) you can give that product to once the project finishes... </li></ul></ul><ul><li>Individuals and interactions </li></ul><ul><ul><li>Get involved with your projects: know how your teams are working together and how they are getting along , enable them to interact with others in the community... </li></ul></ul>
  13. 14. <ul><li>Welcome to the “programme” = jiscRI / SLA </li></ul><ul><li>Your details please (keep updated) = DOAP </li></ul><ul><li>Project Plan Posts (7of7) = Project Blog </li></ul><ul><li>Site Visit (Evaluation) = Baseline </li></ul><ul><li>Progress Posts/Tweets = Blog Planet / Feeds </li></ul><ul><li>Synthesis Liaison (Blog Gnome) = Tags </li></ul><ul><li>Final Progress Post = Project “Argos” Product </li></ul><ul><li>User/Peer Evaluation Panel = Benefits Realisation </li></ul><ul><li>Lessons Learned & Project Sign-off Survey </li></ul><ul><li>Dissemination / ProgEval = Toolshed / INF11Eval </li></ul>
  14. 15. <ul><li>Solution to immediate problems </li></ul><ul><li>over exploring a problem space. </li></ul><ul><li>End user engagement, </li></ul><ul><li>over comprehensive stakeholder agreement. </li></ul><ul><li>Skills of project team, </li></ul><ul><li>over well articulated paperwork. </li></ul><ul><li>Letting the community lead, </li></ul><ul><li>over requiring instructions to be followed. </li></ul><ul><li>*= That is, while there is value in the smaller items, RI values the larger items more. </li></ul>
  15. 16. <ul><li>&quot;Rapid Innovation&quot; builds on the previous success JISC has had in funding short iterative projects that embrace the small motivated team effort of developing solutions hand-in-hand with the end user .  </li></ul><ul><li>Numbers: </li></ul><ul><li>750+ blog posts </li></ul><ul><li>~15 posts per project </li></ul><ul><li>932+ tweets </li></ul><ul><li>3 Events = 1000+ participants </li></ul><ul><li>Public requests for RI projects to Gov’t in Australia, USA and EU. </li></ul>
  16. 17. “ If you want to succeed, double your failure rate” - Tom Watson (IBM) -
  17. 18. % of CHANGE in Technology / Software % of CHANGE in Practice / Processes 2 1 3 ? Programme 4 Programme
  18. 19. COMMUNITY RI ? RI ? Process Change Tool Change Q4
  19. 21. <ul><li>Could this be a strategic pattern in times of recession, e.g. keep our community? </li></ul><ul><li>Do people view programme scoping in terms of process / tool change projects? </li></ul><ul><li>What parts of RI do you find valuable? </li></ul><ul><li>How do you handle large programmes of work? </li></ul><ul><li>How do you build community in your projects? </li></ul><ul><li>What would a process change RI call look like? </li></ul><ul><li>In due course would a cross team RI call be valuable? </li></ul>

×