Why is Configuration Management Needed?
Two fundamental developments are affecting IS/IT development projects, especially in the public sector: • Adoption of PRINCE II means that most planning is now ‘product based’: These products are subject to change and amended requirements and are therefore ‘configuration items’, which must be managed through Configuration Management. • IS/IT projects linked to the business objectives of the organisation: IT developments are no longer isolated and run totally within the IT department. They must fulfil cost / benefit justification and have viable business goals based on those of the organisation. Any change request to the project must therefore have its impact considered across a wider perspective. Adoption of Configuration Management can assist by: • Identifying the project’s deliverables; • Setting the project’s business objectives • Ensuring that each configuration item meets its quality criteria; • Encouraging user involvement by: • Introducing Change Control • Informing users of cha
