Develop a mechanism to manage the required level of IT components quality both during implementation and after. These mechanisms should ensure IT KPIs and benefits shown in project's Business Case and should take into account strategic diversity of required quality levels in different areas of the company.
Projects are launched to adapt company to changing reality. However, after the completion of the project the reality continues to change. Completion of the project on time, within budget and scope is only the beginning of the path. In the long-term systems’ life cycle, more than the scope and the cost of initial functionality, often other aspetcs count even more. The cost of future maintenance, the cost of future developments, costs of future capacity scaling, the cost of future moving to other infrastructure, the costs of future integration, the cost of future repairing data errors, the cost of future testing, the cost of monitoring, etc.
In order to sustain implementation effects for at least few years (as recorded in business case) we have to maintain good health of the IT environment. We also want to ensure responding to the challenges of the market effectively in the long-term. That’s why it is important to specify, both during the implementation and after, strategically required quality parameters of IT architecture and IT components. These company-level requirements will determine the long-term costs of systems’ future changes and maintenance.
Without such mechanisms local objectives of future projects’ (ROI) may win over the company-wide quality requirements what may significantly affect the long-term cost of "living" with developed systems.Read more about: