• Legacy interdependencies

  • DCA tolerances

  • High

    No legacy dependencies, or dependencies are fully understood and the transformation is near complete.

    Off
  • Medium high

    Minimal legacy dependencies that are generally understood.

    Off
  • Medium

    Some legacy dependencies with some testing of assumptions about implications.

    Off
  • Medium low

    Significant legacy dependencies, with minimal testing of assumptions about implications.

    Off
  • Low

    Major legacy dependencies with uncertain implications for the project.

    Off

    • No legacy dependencies, or dependencies are fully understood and the transformation is near complete.

    • Minimal legacy dependencies that are generally understood.

    • Some legacy dependencies with some testing of assumptions about implications.

    • Significant legacy dependencies, with minimal testing of assumptions about implications.

    • Major legacy dependencies with uncertain implications for the project.

  • Deployment and sustainability

    Delivery confidence can be impacted by the deployment strategy. High levels of hyper care, iterative deployment to refine the solution and effort to build capability can improve confidence and minimise risk.

    Large scale, big-bang or fast-paced deployment can lower confidence due to unrealistic estimates of time, cost and benefits, reducing opportunity to develop a solution that suits different business area needs.

    Transition to business as usual (BAU)

  • DCA tolerances

  • High

    Transition to BAU co-created with business, scoped, budgeted and scheduled.

    Off
  • Medium high

    Consultation with business on BAU and accounted for in business case.

    Off
  • Medium

    Consultation with business on BAU and partially accounted for in business case.

    Off
  • Medium low

    Some consideration of transition to BAU, but not sufficiently accounted for in planning. No consultation with business on BAU.

    Off
  • Low

    Transition to BAU considered out of scope.

    Off

    • Transition to BAU co-created with business, scoped, budgeted and scheduled.

    • Consultation with business on BAU and accounted for in business case.

    • Consultation with business on BAU and partially accounted for in business case.

    • Some consideration of transition to BAU, but not sufficiently accounted for in planning. No consultation with business on BAU.

    • Transition to BAU considered out of scope.

  • Next page: Other considerations in determining a DCA

  • Design for a common, seamless experience

     

    Adopt open standards where appropriate: Consider how reuse and open standards can support other services across government. Where appropriate, design and build with them to bring your service to more platforms, improve data sharing capability, prevent vendor lock-in and create familiarity for users.

    Off

Connect with the digital community

Share, build or learn digital experience and skills with training and events, and collaborate with peers across government.

Join the Digital Profession