Solution
Technology
Often digital projects involve innovating with technologies that are unfamiliar or untested, which can affect delivery confidence.
Strategies to elevate confidence include iterative deployment strategies that build capability and confidence. Other areas for attention include interfaces with legacy systems, including the ways new systems interact with, or replace, aging legacy systems, while maintaining essential services.
Aging legacy systems can affect the system stability upon which the transformation may be reliant.
- Legacy system dependencies need thorough analysis.
- Assumptions about legacy data coherence and consistency can be particularly problematic, especially for projects involving transfer to cloud services.
More generally, the solution needs to conform to the technical architecture of the business area.
- For commercial off the shelf software, the degree of fit with business requirements and degree of change that will be required to software or service can reduce delivery confidence.
- For AI-based transformation, detailed understanding of how artificial intelligence (AI) will be used within the business environment is essential, as is consideration of human rights, privacy and ethics implications, particularly for AI.
Consideration should be given for AI solution reliability and safety, and the transparency, explainability and contestability of decisions made using AI solutions. For reference, the Australian Government has developed Australia’s AI Ethics Principles which are foundational to Australia’s safe and responsible adoption of AI.
The policy for the responsible use of AI in government builds on this foundation and aims to ensure that government plays a leadership role in embracing AI for the benefit of Australians.
Delivery Confidence Assessment (DCA) tolerances
-
In-house expertise in the technology. Ability to challenge supplier expertise.
-
Significant in-house familiarity with the technology
-
Some in-house familiarity with the technology.
-
Low in-house experience with the technology. Largely reliant on supplier capability.
-
No in-house familiarity with the technology. Complete reliance on contractor expertise.
Solution context
Because digital solutions are highly interconnected, delivery confidence can be impacted by organisational, procedural, policy, regulatory and human system interdependencies.
Delivery confidence can be:
- Improved when there is evidence of strong alignment with technical architecture, policy and standards, and active management of interdependencies beyond the project’s control.
- Reduced where important factors are outside the project’s control, particularly where policy or legislative reform is required, or where delivery and operational responsibilities are in separate agencies.
Project interdependencies
DCA tolerances
-
Project is largely a closed system with tight boundaries and no critical dependencies outside the project’s control.
-
Project is largely isolated from external influence but has minor well-managed interdependencies outside project control.
-
Project is subject to some external influence, but interdependencies are being actively managed.
-
Project is affected by external influence and is aware of interdependencies.
-
Projects spans multiple departments or agencies, with unclear or complex interdependencies.
Legacy interdependencies
DCA tolerances
-
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
-
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.