Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Tech Radar - Build your own

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →
Avatar for trecenti trecenti
February 18, 2014

Tech Radar - Build your own

Avatar for trecenti

trecenti

February 18, 2014

Other Decks in Technology

Transcript

  1. b u i l d y o u r o

    w n TECH RADAR Improving the process and the outputs.
  2. AGENDA ▫︎The Tech Radar ▫︎A Personal Tech Radar ▫︎An Enterprise

    Tech Radar ▫︎The ThoughtWorks Tech Radar ▫︎Building your own! ▫︎Rackspace Reach Radar !2
  3. !4 “A living document to assess the risks and rewards

    of existing and nascent technologies”
  4. WHY BUILD ONE? ▫︎It helps guiding your career decisions. ▫︎It

    helps restoring the sanity to purchase decisions. ▫︎It steers the technology direction. ▫︎It’s cool. !5
  5. SO IT HELPS YOU TO… Understand what’s happening outside of

    the bubble. Keep you in sync with other nascent technologies. Guide your decisions when investing in other technologies. !8
  6. CHALLENGE & INNOVATION There’s a lot of risk when adopting

    new technologies. Having a company radar help balancing this risks and makes the continuous innovation easier. !10
  7. !12 “For any given technology, your organisation has an ideal

    location on the innovation curve, balancing risk versus reward”
  8. !14 “Technology never sits still; you must (re-)evaluate it constantly

    or risk drastically falling behind your competitors”
  9. A COMMUNICATION TOOL !16 “In most organisations, there is no

    feedback loop from the people who use technology to the people who choose it.”
  10. TECHNOLOGY & BUSINESS ALIGNMENT !17 “A tech radar allows more

    intelligent decision making and career planning”
  11. SCOPE !20 It is “about things you are looking towards,

    not recriminations about the past”.
  12. DEFINING THE THINGS (BLIPS) !22 What’re the things you want

    to capture? ! Categorise them and capture the state TOOLS TECHNIQUES PLATFORMS LANGUAGES & FRAMEWORKS
  13. DEFINING THE CYCLE (RINGS) !23 How fast can you assess

    the things? ! ! ! The lesser the cycles the greater the risk in adoption. HOLD ADOPT
  14. EXECUTION GUIDE !25 ▫︎ Have a white board with your

    structure. ▫︎ Put all the blips (cards) separated by the categories. ▫︎ Have some one facilitate the reading, discussion and placement of them in the rings. ▫︎ Have someone else writing down the motivations for the placement. ▫︎ Review and re-evaluate.
  15. OUTPUT AND DIGITAL VERSION !26 ! The output will be

    a list of things (blips) separated in categories (quadrants) distributed in the adoption lifecycle (rings). ! You can use tools to plot this radar in a digital version github.com/bdargan/techradar
  16. THE PITFALLS !29 ▫︎Long passionate discussions ▫︎Things we couldn’t change

    or assess ▫︎Don’t like vs. not worth assessing ▫︎The “adopt all” symptom ▫︎The hold vs. avoid
  17. THE OUTCOME !30 ▫︎Knowledge sharing ▫︎People in sync with the

    things ▫︎Snapshot of the present ▫︎Better visibility of the future
  18. For questions or suggestions: Bruno Trecenti & Alexandre Nunes !

    For more information, check-out Neal Ford blog-post: http://bit.ly/1hmfwNS THANK YOU