Sublime

For long-time organizations with high technical debt, a strategy to rewrite existing software applications won’t work—it’s just too expensive. Plus, rewriting without making the necessary technical and organizational transformations is a waste of money. Your strategy needs to be a well–considered “layered” strategy where the layers are time.

The key to pursuing speed and adaptability at the same time is to view software technology as a continuously evolving asset, instead of something that is built once and then maintained.

Some takeaways: Work in small teams, create fast feedback cycles, reduce requirements-in-process, improve security hygiene, deliver small pieces of work frequently.

Douglas Hubbard’s book,

Think of traditional organizations in which business analysts, developers, testers, and operations staff operate in separate functional teams. These teams are dependent on each other at a very low level. Even though they may be working toward the same goal, they will inevitably have different priorities. They will also have different processes and

A stream-aligned team aims to produce a steady flow of feature delivery. A stream-aligned team is quick to course correct based on feedback from the latest changes. A stream-aligned team uses an experimental approach to product evolution, expecting to constantly learn and adapt. A stream-aligned team has minimal (ideally zero) hand-offs of work to