CTOs in London "The Challenges of Evaluating Development Technology Within the C-Suite"
4 likes1,680 views
The document discusses the challenges CTOs face in evaluating development technology, emphasizing the need for effective communication of the tech vision, structured evaluation processes, and ongoing knowledge development. It introduces concepts such as framing problems, offering alternatives, and using models like the 'spine model' to aid decision-making. Additionally, it highlights resources for staying informed and improving skills through various learning channels.
CTOs in London "The Challenges of Evaluating Development Technology Within the C-Suite"
- 1. The Challenges of evaluating (Development) Technology within the C-Suite Daniel Bryant @danielbryantuk
- 2. New technology is great... Until it isn'T 11/08/2016 @danielbryantuk App developers with new tech be like F**king new technology... Credit to Michael Hausenblas This has been me many times!
- 3. The pitch • We all know Evaluating technology as a cto is challenging – Balancing multiple constraints while owning the tech vision – Delegation is key... • Core skills – Communicating the tech vision – Evaluation – Developing (and maintaining) knowledge and awareness 11/08/2016 @danielbryantuk
- 4. @danielbryantuk • Chief Scientist at OpenCredo / CTO SpectoLabs ü Transforming organisations through technology and teams ü Ex Academic, web dev, sysadmin, 'full stack Dev', CTO, Consultant ü Microservices, cloud, Containers, Java, Go, Docker, Kubernetes • London Java Community Associate • Adopt OpenJDK and JSR • InfoQ Editor, DZone MVB, VOXXED, O'Reilly 11/08/2016 @danielbryantuk
- 5. Communicate the tech vision 11/08/2016 @danielbryantuk http://blog.gardeviance.org/2015/02/an-introduction-to-wardley-value-chain.html https://speakerdeck.com/acolyer/making-sense-of-it-all
- 6. Communicate the tech Vision 11/08/2016 @danielbryantuk
- 7. Evaluation - first steps • Frame the problem and the general solution • Offer at least two alternatives • State the recommendation (with benefits and drawbacks) • Bonus: engage empathy (Dev/Ops - ops/DeV etc) 11/08/2016 @danielbryantuk
- 8. Evaluation - The’Spine Model • Effective conversations make for effective collaboration • It's a TOOL Problem – As a species, we have always been Tool users and makers. – We use _____ to get our work done • People get stuck in a dilemma where equally plausible options are available • “Going up the Spine” breaks deadlock http://spinemodel.info/explanation/introduction/
- 9. Determine the need for the tool • PRACTICES before Tools – Decide on the Practices that the tools are there to support – We do _____ to create value • PRINCIPLES before Practices – Decide on the Principles to measure those Practices against. – We leverage _____ to change the system • VALUES before Principles – Make as explicit as possible the Values at play in the system. – We optimise for _____ • NEEDS before Values – It all starts at Needs. Why does this system exist in the first place? – We are here to satisfy _____ http://spinemodel.info/explanation/introduction/
- 10. Evaluation - Fitness functions • Evolutionary Architecture – Neal Ford and Rebecca Parsons • Great for evaluation and documentation – Platforms / Language – Middleware – Data stores 11/08/2016 @danielbryantuk
- 11. Evaluation - Matt Raible’s Comparison Framework 11/08/2016 @danielbryantuk
- 12. Evaluation - It'S easy to be tricked 11/08/2016 @danielbryantuk
- 13. Evaluation - beware of bias and heuristics 11/08/2016 @danielbryantuk
- 14. Developing knowledge and awareness • News and trends – Twitter – blog lists (feedly) – Harvard business review • Learning – Coursera – O'Reilly, pluralsight – Books – Academic papers • Developing A DEEP understanding – Write or blog (InfoQ, Voxxed, O'Reilly) – Teach – Present at conferences • Developing others (and learning) – Brown bag lunches – Afternoon lightning talks – Book clubs – Internal conferences 11/08/2016 @danielbryantuk