IVI Framework Viewer

Alignment Planning

B2

Manage updates to the IT business plan to reflect changes in the IT strategy.

Improvement Planning

Practices-Outcomes-Metrics (POM)

Representative POMs are described for Alignment Planning at each level of maturity.

1Initial
  • Practice
    Gather requirements, at least on an informal basis.
    Outcome
    Requirements are captured but may be incomplete or requirements may not reflect business priorities.
    Metric
    # of requirements gathered.
2Basic
  • Practice
    Gather requirements based on consultation with IT personnel.
    Outcome
    The IT business plan may be IT-centric.
    Metrics
    • %/ ratio of Business to IT sourced requirements.
    • % of budget set for contingency.
3Intermediate
  • Practice
    Negotiate and prioritize expectations with input from some business units based on resource constraints.
    Outcome
    There is greater understanding by the some business units for the need to prioritize outcomes given the resource constraints of the IT function.
    Metrics
    • # of business outcomes that have been prioritized with the business.
    • % of high priority outcomes in comparison to all outcomes.
4Advanced
  • Practice
    Ensure collective participation of personnel across the organization in the requirements gathering process.
    Outcome
    organization-wide gathering processes support identification of more robust solutions.
    Metrics
    • # and % of delivered projects versus those identified in business plans.
    • Count by source of requirements (IT, business, or integrated).
5Optimized
  • Practice
    Incorporate inputs from external sources (e.g. key suppliers and customers) in the requirements gathering process.
    Outcome
    A set of requirements exists that includes strategic and operational needs and opportunities.
    Metrics
    • #/Ratio of new requirements introduced outside the planning cycle.
    • # and % of delivered projects versus those identified in business plans.
    • # of strategic and operational requirements identified in IT business plan.
    • Time taken to get a set of requirements.