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.

Build your Own Technology Roadmap!

1,409 views

Published on

Whether it's for your company or your own professional development (or ideally both), everyone should have a technology roadmap. Unfortunately there is no easy path to pre-made wisdom here, but this talk opines on some ideas and approaches to help formulate a roadmap that is relevant, pragmatic and importantly, able to be communicated to others.

Presented at Mastering SAP Technologies 2016

Published in: Technology
  • Be the first to comment

Build your Own Technology Roadmap!

  1. 1. Sascha Wenninger Integration Architect, Blue T Build your own Roadmap!
  2. 2. • Technology Architect • Integration Focus • Co-Founder, Blue T • @sufw About Me
  3. 3. Focus on what’s important Core Context Generic Defines your company, makes money Never “done”, always being refined Directly supports the Core Tends to be bespoke to some extent Necessary to stay in business. Reduce costs, drive to commodity See Subdomains from Domain-Driven Design for more…
  4. 4. Success?
  5. 5. Porter’s Three Strategies… from 1980! A very high-level intro
  6. 6. Strategic Focus and Technology’s Role? “Gets me from A to B” Bells & Whistles Leather SeatsFabric Seats
  7. 7. Choose Boring Tech Image by Le Temps
  8. 8. I stole this idea from Dan McKinley. You should read his writing about this!
  9. 9. • There is a limit to how much innovation a team can swallow • Doing too many new things  😢 • Provides a budget for new things Innovation Tokens I stole this idea from Dan McKinley. You should read his writing about this!
  10. 10. Dogma and Rules 10% Experience 20% Pragmatism 20% Flexibility 10% Minimalism 10% Trends and Future Needs 10% Experiments & POCs 10% Hands-on Participation 10% Vendor Advice 0% The Architect’s Success Formula
  11. 11. Less of this…
  12. 12. More of that… Image by Sean McGrath
  13. 13. As-Is To-Be
  14. 14. As-Is To-Be Chaos Order
  15. 15. Vector-Based Architecture Pervasiveness Time
  16. 16. Vector-Based Architecture Pervasiveness Time Custom Dynpros
  17. 17. • Shows position & movement • Priorities are evident • Flexible: Allows for revisions mid-way Vector-Based Architecture
  18. 18. Vector-Based Architecture Pervasiveness Time Custom Dynpros
  19. 19. Technology Radar Adopt Assess Trial Hold/Reduce • Published by ThoughtWorks • Free since 2010 • Covers general IT • DIY encouraged
  20. 20. • Does it align with our goals? • Is the benefit greater than the holistic cost? • How mature is it? • Are we mature enough to use it? • Do we think it has a future? Does anyone else? • Are we spending ? For each technology choice:
  21. 21. Lifecycle Phases Hold Assess Trial Adopt Don’t start using this Learn more: PoCs, conferences, etc. Try it on a suitable project No-brainer “if you’re not using this, I’ll laugh about it at the pub”
  22. 22. Plot Position and Course Hold Assess Trial Adopt 1 2 3 1: Web Dynpro Floorplan Manager WDA still has many uses, and FPM is the best way to build them with flexibility and consistency. 2: Enterprise Portal Effectively deprecated, with use cases being fulfilled by SharePoint, Fiori Launchpad/NWBC, and other best of breed tools 3: UI5 The framework keeps maturing, tools like WebIDE make development simpler and more consistent. SAP has proven commitment. Previously: Assess
  23. 23. Add Details
  24. 24. • A detailed radar can easily reach 50-100 items. • Be pragmatic • Focus on contentious items • Goal is to guide & start conversations Lather, Rinse, Repeat
  25. 25. 1. Understand what’s important 2. Understand limitations and constraints 3. Assess in context 4. Communicate! In Summary
  26. 26. E: sascha@BlueT.com.au M: +61 403 933 472 Me: http://about.sufw.me @sufw

×