Technology Radar — July 2017
A recent team planning day included a Technology Radar session where, as a team, we could see what our own Technology Radar might look like.
What we did
Each member of the team wrote their tech onto a post-it note. Duplicates were combined. We used numbers 1 to 4 to represent the quarter the tech was placed. And for each tech, the team did a 1–2–3-[vote-by-holding-up-number-of-fingers].
Why we did this
This allowed for the tech to be placed and prioritised into the quarter based on the team’s opinion.
The approach was chosen due to time constraints of the day, and helped to provide a view of our landscape.
I’d imagine future radar planning sessions could include some lead time, whereby the pros-and-cons could be pre-prepared by members of the team. Plus, the merits of each could be discussed to offer some deeper technical perspectives.
What we discovered
Now our team has a nice view of our tech landscape (generated following the details from this Build Your Own Technology Radar post), and it will be interesting to track and compare the movements in our team’s radar.
There wasn’t a distinct winner between React / Angular, however, from having been exposed to React in a recent TuneUp project (PageUp’s awesome internal hackathon), I find myself agreeing with React (the feel of extending code with HTML vs. extending HTML to know code *my very simplistic view starting point).