Building a roadmap for a Frameworks and Infrastructure org
I have been fortunate to get an opportunity to build a backend org that focuses on application architecture and infrastructure. One of my key responsibilities is to constantly prioritize and plan what to build next. But prioritizing the right infrastructure is a hard challenge. Infrastructure components and investments lack the immediate end-user/interactive feedback, and a well formed product requirements. Not to be confused with lack of business value or user impact.
Infrastructure requirements are dependent on next set of business scenarios and capabilities. Business scenarios and capabilities are in-turn dependent on infrastructure maturity and availability. Classic chicken and egg.
Although not a silver bullet, IMO dividing infrastructure roadmaps and tasks into categories might help make progress and clearly think about the next steps.
Bonus: also find a questionnaire to navigate the common planning questions.
Basic foundation work:
- This work helps build the base layer of what Infrastructure should be. These are the fundamental capabilities around security, monitoring, observability, config management, build/release, reliability, scalability, durability etc. This is the infrastructure’s version of the twelve-factor methodology.
