Technology Strategy What is it and why do we need it – Scott Millett – DDD Europe 2019

video:

Domain-Driven Design Europe 2019
https://dddeurope.com

Technology Strategy: What is it and why do we need it? (Talk)

What is a technology strategy? Is it just another form of ivory tower architecture that quickly becomes out-of-date and nobody cares about? Or is technology strategy a vision that helps teams in large organisations to stay aligned, making decisions in the best interest of the organisation as a whole instead of becoming locally-optimising silos? And is there any point in strategy now we’re all agile and everything is constantly changing?

Proponents argue that, when implemented correctly, a technology strategy improves team autonomy and agility even in constantly-changing, digital environments. They argue that technology strategy clarifies key business capabilities. They argue that technology strategy identifies platform deficiencies that need to be addressed in order for teams to build and manage services at greater speed and with reduced costs. They also argue there are lots of other benefits to technology strategy, but should we believe them?

In this talk we’re going to explore technology strategy. We’re going to look at some real examples of tech strategy and understand exactly what it is. After this talk, you’ll know whether technology strategy is something you should be paying more attention to, or whether it’s something you can happily ignore and focus on shipping stuff instead.

Biography

Scott Millett is the Director of IT for Iglu.com, and has been working with .NET since version 1.0. He was awarded the ASP.NET MVP in 2010 and 2011, and is the author of Patterns, Principles, and Practices of Domain-Driven Design, Professional ASP.NET Design Patterns and Professional Enterprise .NET.

Tags

Follow us

Read our latest news from Virtual DDD on any of these social networks!

Recent videos

Impact Mapping – The Secret Sauce

Details "Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and...

Pragmatic Architecture: How to Know When It’s Enough

Details Overengineering wastes time and effort, while underengineering creates future pain. How do you strike the right balance? This talk explores how you can use the balanced coupling model to achieve the just-right engineering. You’ll learn to predict volatility of...