When you replace or significantly modify components of a larger system, too frequently we focus on whether the code we are building functions correctly. This is important, but it’s also short-sighted. It’s easy to introduce errors because we are changing interactions. Coding bugs are only one quality problem.

In traditional agile approaches, retrospectives are valuable to team improvement. However, when teams encounter organizational issues beyond their control, such as project structure, interorganizational communication, or resources, it's more difficult. Here's how to expand continuous improvement to the whole company.

There is a big difference between a troubled project and a disaster, and not being clear about the distinction is hazardous to decision-making. If a project you're managing is in danger of missing deadlines, that doesn't mean it's out of control—you just need to explain to stakeholders how it can get back on track.