There are many things your team could do over the next year or two. How do you decide which of them to prioritize?
The answer should be that you are guided by your technical strategy, but often, that strategy is undocumented. It exists because how you approach challenges and what you choose to do IS your strategy. But if it isn't written down, you may find different people have very different views about what you should be focussing on, and teams will make decisions for local reasons that may not support the needs of the whole organisation.
Documenting your strategy is important, but it's only the first step. You need to communicate it effectively so that people can use it to make decisions. And finally, you need to track your progress: are you delivering what you need to? Is the strategy still the right one?
In this session, I'll cover:
- What makes a good technical strategy
- How to document it
- How to use it to align different teams
- How to track progress and adapt to change