One organization I worked in had a release-readiness review that every feature went through: a form, an architect's sign-off, and a final thumbs up from a senior leader. When that leader left, the review lost its teeth. Teams still filled out the form. Nobody checked the answers, and nobody owned any section of it. It had turned into a collection of things various groups wanted to know to be able to provide their appropriate lens of support, but no one was really looking at readiness as a whole.
The House of Software Value Delivery has three kinds of Tools, and each does a different job.
Tools below the foundation improve the ecosystem's Attributes: how leaders meet, how planning runs, how functions make tradeoffs together.
Tools between the foundation and the pillars improve the software's Attributes: code review practices, architectural standards, how you prioritize technical debt.
Tools above the pillars validate the software's Attributes. They check whether the software is actually Secure, Scalable, and Supported before it reaches users.
The readiness review originally functioned as a validation Tool. Years later, it still existed and still ran on schedule, but it had stopped validating anything.
Tools drift. A practice built for one job, by people who cared about that job, keeps running after those people move on, and the job falls away while the ritual stays.
We rebuilt the review with partners from across the organization. Each section got an owner who defined its questions and an escalation path. Assessments started at the beginning of the release cycle, months ahead of release, and the questions changed by phase: security received a focus at initial release, performance when scaling, and documentation at general availability. Teams started using it to shape scope and timelines, well before anyone needed a sign-off.
So I ask two questions about every Tool. Which job is it doing: improving an Attribute, or validating one? And is it still doing that job?
I created the House of Software Value Delivery to give every Tool a place in the structure, so you can see what each one is there for. It also makes the Tools that aren't supporting any Attribute easy to spot. Part of my work is removing those. Every Tool costs teams time and attention, and one that doesn't move anything is just overhead.
