Establishing a repeatable improvement process
In Chapter 1, Setting Targets and Identifying Problem Areas, we learned about the potential negative impacts of poor BIS performance. It is great to have knowledge, metrics, and tools to resolve performance issues. However, a behavior that is seen too often is that these are usually leveraged reactively after an issue has had enough of an impact on the business that it is formally raised and brought to the attention of developers and administrators. This is not a good situation to be in for reasons described in the following points:
- Production changes: These changes are non-trivial and require careful change management. Change management involves more than just deploying new technical artifacts. One example is that users may need training and documentation may need to be updated if there are significant reports or semantic model-level changes.
- Short deadlines: There may be deadlines for the business to resolve performance issues...
