-
In-house expertise in the technology. Ability to challenge supplier expertise. User excitement with the solution.
-
Significant in-house familiarity with the technology. User acceptance of the solution.
-
Some in-house familiarity with the technology. User tolerance of the solution.
-
Low in-house experience with the technology. Largely reliant on supplier capability. Users have had minimal exposure to the technology.
-
No in-house familiarity with the technology. Complete reliance on contractor expertise.
Your responsibilities
To successfully meet this criterion, you need to:
- ‘build once, use many times’
- design for a common, seamless experience
- reuse data where you can
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.
Assessment of delivery confidence should consider adherence to relevant policies and frameworks, such as security policies, that may affect the ability to go-live.
Delivery confidence can be 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. Solution context has been addressed through assessment related to project interdependencies and legacy dependencies.
DCA tolerances
High
Project is largely a closed system with tight boundaries and no critical dependencies outside the project’s control.
Off
Medium high
Project is largely isolated from external influence but has minor well-managed interdependencies outside project control.
Off
Medium
Project is subject to some external influence, but interdependencies are being actively managed.
Off
Medium low
Project is affected by external influence and is aware of interdependencies.
Off
Low
Projects spans multiple departments or agencies, with unclear or complex interdependencies.
Off-
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.
Project interdependencies
‘Build once, use many times’
Apply reuse in decision making: Use the Australian Government Architecture to understand the tools, capabilities, policies and standards for building government services. Identify and document how they are applied in your decision making.
Apply learnings from predecessors: Reach out to teams and agencies for their experiences and lessons creating similar services and how to apply them to yours.
OffLegacy 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.