Organizations suffer from low value artifacts. This incurs technical debt and needs to be addressed, just as with any other asset owned by the business.
- The first step is identifying the pain points and artifacts around those areas.
- A prioritization is then undertaken to determine which artifacts need to be discarded, improved upon, or left alone.
- For any artifact requiring change, an appropriate impact analysis needs to be conducted.
This template will help you document your current state and future state as well as the impact across design, development, testing, and deployment.