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.

Is Continuous Adoption in Software Engineering Achievable and Desirable?

1,701 views

Published on

ICSE 2016 Software Engineering in Practice keynote.

Continuity in software development is all about shortening cycle times. For example, continuous integration shortens the time to integrating changes from multiple developers and continuous delivery shortens the time to get those integrated changes into the hands of users. Although it is now possible to get multiple new versions of complex software systems released per day, it still often takes years, if ever, to get software engineering research results into use by software development teams. What would software engineering research and software engineering development look like if we could shorten the cycle time from taking a research result into practice? What can we learn from how continuity in development is performed to make it possible to achieve continuous adoption of research results? Do we even want to achieve continuous adoption? In this talk, I will explore these questions, drawing from experiences I have gained in helping to take a research idea to market and from insights learned from interviewing industry leaders.

Published in: Software
  • Be the first to comment

Is Continuous Adoption in Software Engineering Achievable and Desirable?

  1. 1. Is Continuous Adoption in SE Achievable and Desirable? Gail C. Murphy
 University of British Columbia
 Tasktop Technologies Inc. @gail_murphy
  2. 2. 2
  3. 3. IMPACT 2
  4. 4. Stop thinking
 linearly
  5. 5. Start thinking about multiple paths to impact(s) in research and practice 4
  6. 6. Start thinking about multiple paths to impact(s) in research and practice 4
  7. 7. Overview 5
  8. 8. Overview 5 Mylar Story Impact Model How is research influencing the practice of software engineering?
  9. 9. OverviewContinuous Integration Vignette Innovation Adoption in Practice 5 How is innovation occurring in the practice of software engineering?
  10. 10. Innovation Adoption in Practice 6 Mylar Story Impact Model Continuous Integration Vignette Overview
  11. 11. Innovation Adoption in Practice 7 Mylar Story Impact Model Continuous Integration Vignette The Mylar/ Tasktop Story A story about paths to impacts in research and practice
  12. 12. 8
  13. 13. TIMELINE 2004 Mylar 8
  14. 14. TIMELINE 2004 Mylar Information Overload 8
  15. 15. TIMELINE 2004 Mylar Information Overload 8
  16. 16. TIMELINE 2004 Mylar Information Overload Mylar
 
 See only what you’re working 8
  17. 17. TIMELINE 9 2007 Tasktop Mik Kersten Rob Elves 3 Co-founders Gail Murphy Shawn 
 Minto Leo Dos Santos 2 Staff 2004 Mylar
  18. 18. TIMELINE 10 2016 Tasktop 2004 Mylar
  19. 19. TIMELINE 11 2004 Mylar 2016 Tasktop Neelan Choksi
 (President/COO since 2010) Staff
  20. 20. TIMELINE 11 2004 Mylar 2016 Tasktop Neelan Choksi
 (President/COO since 2010) Staff
  21. 21. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporate Monday
  22. 22. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporate Monday
  23. 23. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporate Monday IBM
 Trial
  24. 24. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporate Monday IBM
 Trial Publication
  25. 25. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporate Monday IBM
 Trial Publication Robustness & community building
  26. 26. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporated Monday IBM
 Trial Publication
  27. 27. Mylar Highlights: 2004-2007 2004 2004 2005 2005 2005-06 2007 Mylar invention & innovation 1st industrial trial at IBM Toronto 1st academic publication EclipseCon/Field Study/Eclipse project Company discussions; biz competitions Mik’s Ph.D. Friday; incorporated Monday IBM
 Trial Publication
  28. 28. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Mylyn/Tasktop Highlights: 2007-2016
  29. 29. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Mylyn/Tasktop Highlights: 2007-2016
  30. 30. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Mylyn/Tasktop Highlights: 2007-2016
  31. 31. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Mylyn/Tasktop Highlights: 2007-2016
  32. 32. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Mylyn/Tasktop Highlights: 2007-2016
  33. 33. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Users thought Tasktop/Mylyn had deleted their code! Mylyn/Tasktop Highlights: 2007-2016
  34. 34. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Users thought Tasktop/Mylyn had deleted their code! Solution was to add one line instruction Mylyn/Tasktop Highlights: 2007-2016
  35. 35. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Users thought Tasktop/Mylyn had deleted their code! Solution was to add one line instruction Mylyn/Tasktop Highlights: 2007-2016
  36. 36. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Mylyn/Tasktop Highlights: 2007-2016
  37. 37. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Mylyn/Tasktop Highlights: 2007-2016
  38. 38. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovations Mylyn/Tasktop Highlights: 2007-2016
  39. 39. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovationsVarious inventions Mylyn/Tasktop Highlights: 2007-2016
  40. 40. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovationsVarious inventions Mylyn/Tasktop Highlights: 2007-2016
  41. 41. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovationsVarious inventions Mylyn/Tasktop Highlights: 2007-2016
  42. 42. 2007 2008 2009 2011 2014 2015-16 Mylar becomes Eclipse Mylyn Tasktop Dev Tasktop Dev - Enterprise sales Tasktop Sync $11M Series A funding Tasktop Data & Gateway capabilities Eclipse Mylyn Various innovationsVarious inventions Continual innovation & incremental validation Mylyn/Tasktop Highlights: 2007-2016
  43. 43. Robustness & community building
  44. 44. Robustness & community building Continual innovation & incremental validation
  45. 45. Innovation Adoption in Practice 23 Mylar Story Impact Model Continuous Integration Vignette Innovation in Practice A story about paths to impacts in practice from practice
  46. 46. Continuous Integration Problem: Slow discovery of integration problems slows development and delivery Shared Repository Thanks to https:// www.thoughtworks.com/continuous- integration Automated Fast Builds Self-testing Builds Everyone commits to baseline each day Automate Deployment Build every commit on integration machine 24
  47. 47. Research Impact Impact Practice Buildbot, Travis CI, Django-Jerkins... Various
 innovations Continuous Integration Many tools evolving in
  48. 48. Research Impact Impact Practice Continuous Integration Various
 innovations Practice is not still Practice is always innovating
  49. 49. Innovation Adoption in Practice 27 Mylar Story Impact Model Continuous Integration Vignette Adoption of Innovations How are innovations generally adopted in practice?
  50. 50. 4 financial, insurance, retail e-commerce Interviews of Technology Leaders 1 2 cloud 28 SME
  51. 51. SME Fortune 100 IPO Technology Adoption Curve Innovators Early Adopters Late Majority Laggards
  52. 52. SME Fortune 100 IPO Technology Adoption Curve Innovators Early Adopters Late Majority Laggards
  53. 53. SME Fortune 100 IPO Technology Adoption Curve Innovators Early Adopters Late Majority Laggards
  54. 54. SME Fortune 100 IPO Technology Adoption Curve Innovators Early Adopters Late Majority Laggards
  55. 55. SME Fortune 100 IPO Technology Adoption Curve Innovators Early Adopters Late Majority Laggards
  56. 56. Interview about Innovation Adoption Process and philosophy Factors Awareness and spread
  57. 57. Process and Philosophy
 for Innovation Adoption Managed but Individual Add to Value Stream Cost-effective in Environment
  58. 58. Factors Affecting Innovation Adoption Open before Closed People and Technology Credibility & Momentum Developer Happiness
  59. 59. Hacker News, Reddit,
 Peers, Meetups/ Conferences, 
 “Work Out Loud”, Surveys,
 Papers (non-SE) Tech talks, Dev days, Team Comparisons
 Spread
  60. 60. Research Impact Impact Practice Adoption of Innovations in Practice is… frequent of impactful 
 technologies when possible
  61. 61. Innovation Adoption in Practice 35 Mylar Story Impact Model Continuous Integration Vignette Adoption of Innovations How are innovations generally adopted in practice?
  62. 62. Research Invention creation or design of something that has not existed before e.g., the incandescent lightbulb
  63. 63. Research Innovation about the use of an idea of method e.g., iPhone
  64. 64. Research Invention creation or design of something that has not existed before e.g., the incandescent lightbulb Innovation about the use of an idea of method e.g., iPhone
  65. 65. Research Invention creation or design of something that has not existed before e.g., the incandescent lightbulb Innovation about the use of an idea of method e.g., iPhone Both “I”s are important
  66. 66. Research Invention creation or design of something that has not existed before e.g., the incandescent lightbulb Innovation about the use of an idea of method e.g., iPhone Both “I”s are important Innovation builds from earlier inventions and innovations
  67. 67. Research Invention creation or design of something that has not existed before e.g., the incandescent lightbulb Innovation about the use of an idea of method e.g., iPhone Both “I”s are important Innovation builds from earlier inventions and innovations Research is the base
  68. 68. Research Invention creation or design of something that has not existed before e.g., the incandescent lightbulb Innovation about the use of an idea of method e.g., iPhone Both “I”s are important Innovation builds from earlier inventions and innovations Research is the base It takes almost as much creativity to understand a good idea as to have it in the first place. - Alan Kay
  69. 69. Forrester Research, TechRadar™: Continuous Software Delivery, Q2 2015" Research is having impact Tech Radar image removed for licensing reasons. Image showed that static analysis tools, version management, etc. from SE research community have impact in SE in practice.
  70. 70. Research Impact Impact Practice Various
 Continuous Integration
  71. 71. Research Impact Impact Practice Technology Adoption
  72. 72. Research Impact Impact Practice Various
 Continuous Integration Research Impact Impact Practice Technology Adoption
  73. 73. Research Impact Impact Practice Various
 Continuous Integration Research Impact Impact Practice Technology Adoption Practice innovates continually
  74. 74. Research Impact Impact Practice Various
 Continuous Integration Research Impact Impact Practice Technology Adoption Practice innovates continually Innovation is required to take Research into impact in Practice
  75. 75. Research Impact Impact Practice Various
 Continuous Integration Research Impact Impact Practice Technology Adoption Practice innovates continually Innovation is required to take Research into impact in Practice Innovation requires understanding of Practice
  76. 76. 42 Thanks to… Mylar + Early Tasktop: Tasktopians circa 2013 Mik Kersten, Rob Elves, Shawn Minto, Davor Cubranic, Taivo Evard, Nathan Hapke, 
 Wesley Coelho, Meghan Allen, Leo Dos Santos, Steffen Pingel Reid Holmes and my research group for suffering through practice talks: Daniel Almeida, Julius Davies, Michalis Famelis, Marc Palyart, Albert Thompson, Giovanni Viviani
  77. 77. Continuous Integration Vignette Technology Adoption in Practice 43 Mylar Story Impact Model Summary
  78. 78. Continuous Integration Vignette Technology Adoption in Practice 43 Impacts
 in
 research and practice Mylar Story Impact Model Summary
  79. 79. Continuous Integration Vignette Technology Adoption in Practice 43 Continual innovation in and by practice Impacts
 in
 research and practice Mylar Story Impact Model Summary
  80. 80. Continuous Integration Vignette Technology Adoption in Practice 43 Continual innovation in and by practice Open 
 before closed Impacts
 in
 research and practice Mylar Story Impact Model Summary
  81. 81. Continuous Integration Vignette Technology Adoption in Practice 43 Continual innovation in and by practice Open 
 before closed Impacts
 in
 research and practice Think about paths to impact(s Mylar Story Impact Model Summary
  82. 82. I do not want you to leave this talk thinking… •Every research project needs impact in practice
 •Every research project should result in an open source project
 •It is good enough to transfer people to Practice
 •Having impact in practice requires creating a company
  83. 83. 45
  84. 84. Is Continuous Adoption in SE Achievable and Desirable? 45
  85. 85. Is Continuous Adoption in SE Achievable and Desirable? 45 It is happening
  86. 86. Is Continuous Adoption in SE Achievable and Desirable? 45 It is happening Much more often from practice, driven by need to solve problems, not from SE research
  87. 87. Research Impact Impact Practice 
 engage with the practice of software engineering convey (blog?) results in terms of problems in practice
 create and nurture an open source project commercialize a technology collaborate with industrial partner track results and share the stories
 and more... Some Actions on the Paths to Impact in Practice
  88. 88. Think about the paths to impact in research and practice for your 
 projectsResearch Impact Impact Practice Challenge: Take at least one of your projects from research to practice Gail C. Murphy
 University of British Columbia
 Tasktop Technologies Inc. @gail_murphy

×