Rework – The measure of waste in the execution of any process, becomes institutionalized with the acknowledgement that progress cannot be made until there is a mastery of situations. The fallacy of managing is in the assumption that what is lacking can be managed. Coupled with the inability to overcome the inevitable knowledge gap for any activity in realizing business outcomes, the art of managing includes acceptance of rework as a necessary precondition to learning. The issue occurs when the learning fails to translate into artifacts that become building blocks, reusable components or stepping stones but instead remain amorphous nuggets of incomplete relics that will be complete at some point in the uncertain future.
This issue can be avoided with Virtually Managed Software. We can make progress.
The key role of architecture is to provide a foundation, a framework and a clarification of the order of things. When the central architectural underpinning of a software product line, an organization or an enterprise is far from certain, rework is unavoidable. Thus to avoid valueless rework, an architectural foundation is a prerequisite.
To fast forward to an expected outcome, one that delivers progress must depend on milestones. Every milestone is a step along the journey towards the destination. It is essential to be able to choose the class or problems or issues that are in focus, and by improving an area with an architectural approach is to acknowledge that an orderly path is possible which must be found.
The only way to reach the point of careful progress is to leave definite artifacts at each milestone. Artifacts that encapsulate the value created, yet provide a path to the value yet to be created. This is the only way to ensure that we are making progress, or can make progress.