IVI Framework Viewer

Representative POMs are described for Architecture Processes at each level of maturity.

1Initial

• Practice

  Start to define and use some Architecture design processes across specific projects.

  Outcome

  Projects show some improvement due to less redesign and rework.

  Metric

  No metrics at this level.

2Basic

• Practice

  Define and use an Architecture design processes across multiple projects.

  Outcome

  Project improve time to market through applying architecture design processes. Less redesign and reworking as a result.

  Metric

  % of project portfolio adhering to architecture processes

3Intermediate

• Practice

  Adopt an architecture lifecycle that is consistent across IT. Embed architecture milestones into all project plans and projects, do not move forward until architecture milestones have been satisfied. Publish and internal guide that defines what is expected of architects in terms of artefacts at different stages of a project. Establish a catalogue of architecture artefact as a shared repository (configuration management database) that is well catalogued and accessible to all key stakeholders.

  Outcome

  Projects consistently deliver quality solutions and can provide traceability of design decision to business requirements. Project stages are generally understood just by knowing where in the architecture process they are. Confidence in ability to delivery quality through adherence to architecture process.

  Metric

  Ave Age of Artefacts in Shared Repository # Days since last contribution to Share Repository % Contributors without publications in Shared Repository

4Advanced

• Practice

  Integrate the architecture processes across the business and IT so that architecture governance is part of IT governance. Have the repository link together, artefacts in different layers (i.e. business, data, application, technical, infrastructure, etc.). Define and publish a model describing the architecture engagement process for project managers, contractors etc., containing both process and information artefacts.

  Outcome

  Architecture processes are applied by default though the application of project or change management processes and are seen as integrated process.

  Metric

  % of project portfolio adhering to architecture processes % of architecturally significant projects without a named architect assigned

5Optimized

• Practice

  Adapt the architecture processes to the business operational model and extend them to address requirements across the business ecosystem.

  Outcome

  Can deal with range of delivery methods but continue to follow architecture processes which retains the value derived through good governance, reuse and information sharing.

  Metric

  % of Interventions directly attributable to Architecture % of project portfolio defined as architecturally significant