🤝 A release is what unifies Engineering and Business

Some feedback on yesterday's post (What is a release):

What specifically flows into the two points? Value? Effort?

Perhaps a better way to phrase this is these are the two points of focus that unify the development team with the rest of the business organization. And the release is the container.

Documentation, specifications, innovation, new technology, etc. flow into the useful point.

Testing and automation flow into the confidence point.

The business value that flows out of the useful point is user value, profit, increasing sales, etc.

From the confidence point flows quality and responsiveness.

But these two points give us a simple way to focus and evaluate a release - is it any good? Is everything we are doing as engineers contributing to these points?