Remove Software Architecture Remove Speed Remove Strategy Remove Systems
article thumbnail

How architecture evolves into strategy

O'Reilly Software

A look at the roles of architect and strategist, and how they help develop successful technology strategies for business. I should start by saying this section does not offer a treatise on how to do architecture. Technology systems are difficult to wrangle. Our systems grow in accidental complexity and complication over time.

Strategy 100
article thumbnail

All In

The Agile Manager

IBM had launched the trademarked Personal Computer in 1981 using an open architecture of widely available components from 3rd party sources such as Intel and the fledgling Disk Operating System from an unknown firm in Seattle called Microsoft. In 1987, IBM introduced a new product, the Personal System/2.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Forming an Architecture Modernization Enabling Team (AMET)

Strategic Tech

The figure below shows the typical life-cycle of an architecture modernization initiative, including commonly observed points where we have observed AMET formation. Their technology landscape has a high level of what they consider to be legacy or heritage systems — monolithic systems with tens or hundreds of developers working in them.

article thumbnail

Alignment Efficiency: When to Sacrifice Speed for Greater Alignment

Strategic Tech

Ideally, all of our teams would be delivering at maximum speed and would all be heading in the same direction, highly-aligned with business goals. Unfortunately, we need to balance speed and alignment, and how we make this trade-off is not clear because not all alignment has the same cost. Aligned Autonomy ?

article thumbnail

Visualising Sociotechnical Architecture with DDD and Team Topologies

Strategic Tech

I’ve been disappointed for a long time with the way in which companies organise software development teams. I remember as a young, naive software developer, I assumed there would be structured processes and patterns similar to those used for designing a software architecture.

article thumbnail

The Challenges and Traps of Architecting Sociotechnical Systems

Strategic Tech

Loosely-coupled teams enabled by loosely-coupled software architecture is one of the strongest predictors of continuous delivery performance and organizational scaling. Decoupling Streams of Work Our goal when designing systems is to maximise the speed of delivery and value of the work we deliver.

Systems 40
article thumbnail

A Clash of Mindsets: When New Products Depend on Existing Products

Strategic Tech

This can become delicate when the mindsets of each teams are optimising for different things, most commonly speed vs reliability. The system needs to be highly reliable because even just a little downtime can alienate loyal customers. A good engineering organization moves at speed with high reliability.