One way to assess the long-term health and viability of a product is the to measure the degree to which business leaders and technical leaders collaboratively manage that product's underlying technical architecture. In this Collaboration at Scale webinar, we explored frameworks and processes for managing those technical architectures, including technology radars, sunset grids, and upgrade rules. Collectively, these techniques allow you create a healthy balance of technical improvements and customer/user-facing capabilities that produce long term success.
Luke Hohmann: Luke Hohmann is the founder and CEO of Conteneo In.(formerly the Innovation Games Company). Conteneo's enterprise software platforms and professional services merge collaboration frameworks, data analytics, and domain expertise to help organizations optimize decision making in the areas of strategy, innovation, sales, product development, and market research. Luke is also co-founder of Every VoiceEngaged Foundation, a 501(c) 3 nonprofit that helps citizens, governments, and other nonprofit organizations collaborate at scale to solve technical and wicked problems.
Answer: No. I think the right sequence is to create Visible Architectures of your current/as-is architecture and if needed your desired/to-be architecture. These should then be added to your roadmap or Prune the Product Tree framework in the roots. Once these items have been properly strategically prioritize they can be added to the backlog for execution.
Answer: The first step is to actually have a standard: Something that you can share, reference and enforce. This is the key to preventing ͞reinvention͟. From there, a Visible Architecture plus video explanations is a significant improvement step.
Answer: Don’t confuse writing a Product Backlog Item (PBI or story) with prioritizing it. Let’s review the primary responsibility of the Scrum guide: ͞The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. ͞ This means that the PO should clearly be prioritizing technical work because technical investments contribute to significant value.