Entrowise Blog
Insights on software delivery, technology leadership, and the PPA Method.
-
Your Delivery Pipeline Is Overloaded. Here's Why It Stays Invisible.
Scrum solved something genuinely hard. Inside a sprint, a team's capacity is understood, commitments are visible, and WIP is bounded. For a single team working on well-defined work, this is a real achievement. Most large software organizations have this working reasonably well at the team level. Go up one level to program or portfolio, and the picture breaks down completely. Why portfolio-level workload is so hard to see In large, complex delivery systems, work at the program and portfolio le
-
FROM AGILE COACH TO DIAGNOSTIC LEADER: THE NEXT CHAPTER IN YOUR PRACTICE
What experienced Scrum Masters, Agile coaches, and program managers find on the other side of framework mastery There comes a point in most Agile coaching careers where something quietly shifts. You have the certifications. You know the ceremonies better than most people in the room. You can facilitate a retrospective in your sleep, run a PI planning event without checking your notes, and coach a team through a difficult sprint review without losing the thread. And yet. The same problems keep
-
When the System Is the Problem: Understanding Unintended System Conditions in Software Delivery
Most delivery leaders I know are good at describing what is going wrong. Missed deadlines. Unstable releases. Teams that feel perpetually overloaded. Forecasts that never hold. What is much harder — and I have seen this across dozens of organizations — is explaining why it keeps happening. Not the surface reason. The real one. The one that survives every retrospective, every process improvement, every framework adoption. The answer is almost never the team. And it is almost never the technolog
-
Managing Is Doing. Leading Is Seeing.
You've solved this problem before. You're certain of it. Different quarter, same conversation, same tension, same outcome. Somehow it's back. If you're a good manager, and most people reading this are, your instinct is to work the problem harder. More process, more follow-up, tighter accountability. And it helps. For a while. Then it comes back again. This isn't an effort problem. It's a visibility problem. And closing that gap is what separates managing from leading. When I work with delive
-
The Plan Was Detailed. That Was the Problem.
Nobody builds a bad plan on purpose. The scope document looked thorough. The requirements were signed off by the right people. The milestones had owners. The launch date was in the calendar. Six months ago, in the room where all of this was agreed, it felt like the responsible thing to do. Six months later, the team is sitting with two documents that do not agree. The original plan assumed users wanted a self-serve onboarding flow. Six weeks of beta testing showed they want a guided one. The i
-
Your Priorities Are Clear. Your Trade-offs Are Not.
Here is a conversation that happens in most technology organizations at least once a quarter. A senior stakeholder walks into a planning meeting with a new initiative. It is urgent. There is a real business reason behind it. The ask is reasonable: "Can we fit this in?" The room looks at the backlog. Nobody wants to say what fitting it in actually means. So they say yes. The initiative joins the list. The list now has nine things on it instead of eight. What just happened to items three through
-
Types of Software Delivery Problems
After working with dozens of software delivery organizations, I believe almost every delivery problem falls into one of three categories. Most leaders know two of them well. The third is where careers get stuck. The first is the Technical Problem. Something is wrong with how the solution is designed, built, or verified. A flaw in the architecture. A gap in test coverage. A coding decision that made sense at the time and is now causing pain. These problems are visible, diagnosable, and the ind
-
The Constraint Nobody Is Talking About
Why software delivery keeps failing for reasons everyone can see but nobody names I have sat in hundreds of delivery reviews over the past two decades. Retrospectives, quarterly planning sessions, post-mortems, leadership offsites. The problems on the whiteboard change. The faces around the table change. The tools, the frameworks, the vocabulary — all of it changes. The problems do not. Same missed commitments. Same coordination failures. Same gap between what gets built and what the business