liveBook · Manning

Portfolio-based approach

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A portfolio-based approach manages multiple initiatives as a balanced set of investments across different time horizons and objectives.

A portfolio-based approach manages initiatives as a balanced set of investments, connecting technical decisions to business outcomes across different time horizons. It combines short-term wins with deliberate action on fundamental, long-term challenges. section 3.4

Apply the approach by:

  • Treating each business subdomain as an investment opportunity and varying modernization effort according to its potential business return. section 10.0
  • Investing more in strategically important areas, where speed, control, innovation, and collaborative discovery matter most. section 10.0
  • Using proportionate solutions elsewhere, such as off-the-shelf tools, outsourcing, simple forms over data, or low-code solutions. section 10.0

Balancing modernization horizons

An organization may prioritize immediate value while continuing to address a monolithic legacy database coupled to everything. A strategically important subdomain might justify in-house development, product discovery, and EventStorming, while a low-impact capability may need only a simple CRUD interface. section 3.4 section 10.0

Figure 10.1 This chapter shows how to take a portfolio perspective and verify each candidate value stream fits into the bigger picture.

Use the portfolio view to verify that each candidate value stream contributes to the wider strategic picture. section 10.0

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Explains portfolio allocation across business, organizational, and technical investments, using business subdomains as the primary model.
Examples
Uses a monolithic legacy database, CRUD interfaces, forms over data, low-code solutions, outsourcing, and EventStorming.
What you can do after
Evaluate modernization investments by business importance, expected return, time horizon, and required organizational or technical capability.
How it connects
Connects business objectives, architecture modernization, business subdomains, value streams, product discovery, and EventStorming.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.