-
Delivery Confidence Assessment (DCA) tolerances
-
Adopt transparent data handling
Consider privacy, consent, and control: Safeguard user data by adhering to the Australian Privacy Principles and the Privacy Act (1988). Always obtain explicit, informed consent before collecting a user’s data and provide a means to update or delete it. Allow users to report inaccurate data and respond with how it has been rectified. Notify users of their own responsibilities to protect their data, such as not to share their password with others.
Eliminate ambiguity in your user interface: Provide validating feedback and progress tracking as users interact with your service. Design to eliminate the need for error messages in the first place; make them understandable and actionable where they remain. Tell users what information they need before they start a task and, where appropriate, allow them to pause and resume at their own pace.
Off -
High
The project schedule covers the entire scope for the solution, is used to inform management action and is actively updated. Progress assessed on estimate to complete. There is sufficient contingency for the risk of the project
Off -
Medium high
A schedule measurement baseline exists with a critical path. This provides the basis for management of change.
Off -
Medium
The schedule appears accurate but is not actively updated. Measurement against baseline is not consistent or regular.
Off -
Medium low
The schedule appears mostly complete but is not being used to inform management action.
Off -
Low
The schedule does not cover the complete scope. The critical path is not being managed. The schedule is not being used to support management action. Progress assessed on time spent. No contingency.
Off -
-
The project schedule covers the entire scope for the solution, is used to inform management action and is actively updated. Progress assessed on estimate to complete. There is sufficient contingency for the risk of the project
-
A schedule measurement baseline exists with a critical path. This provides the basis for management of change.
-
The schedule appears accurate but is not actively updated. Measurement against baseline is not consistent or regular.
-
The schedule appears mostly complete but is not being used to inform management action.
-
The schedule does not cover the complete scope. The critical path is not being managed. The schedule is not being used to support management action. Progress assessed on time spent. No contingency.
-
-
Cost and finance
Delivery confidence can be higher where there is evidence of regular monitoring of cost, value and revenue, with any variation attributed to specific causes and with appropriate delegations.
The DCA should consider whether the baseline cost estimate is realistic, or whether there is evidence of optimism bias, or underestimation of budgets and overestimation of benefits to facilitate initiation.
Funding continuity can also affect delivery confidence. Factors to consider include the budget allocation for development after go-live, and to support the training and organisational change management activities needed to realise benefits.
Budgets also need to cater for recurrent costs post implementation, for example, accounting for ongoing operating expenditure (Op-Ex) to support cloud-based digital solutions.
-
DCA tolerances
-
High
Cost, value and revenue are realistically estimated, forecast and monitored continuously. The project is at, or ahead of, budget
Off -
-
-
Medium high
Cost, value and revenue are forecast and monitored regularly. The project is at, or ahead of, budget.
Off -
Medium
The project is at, or ahead of, budget. Cost is monitored regularly.
Off -
Medium low
The project is behind budget. Cost is monitored regularly.
Off -
Low
Cost is not actively monitored. The project is over budget or there is no certainty of current status.
Off -
-
Cost, value and revenue are realistically estimated, forecast and monitored continuously. The project is at, or ahead of, budget
-
Cost, value and revenue are forecast and monitored regularly. The project is at, or ahead of, budget.
-
The project is at, or ahead of, budget. Cost is monitored regularly.
-
The project is behind budget. Cost is monitored regularly.
-
Cost is not actively monitored. The project is over budget or there is no certainty of current status.
-
-
Scope and change control
The abstract nature of digital solutions can make scope management more difficult than for projects with tangible outputs. Robust scope management and change control processes are needed that drive management action.
Scope definition should include data management and conversion, integration and interfacing, reporting, change management, as appropriate.
- During scoping, projects should engage in rigorous up-front analysis about overarching design, consideration of options, critical interdependencies and business problem identification.
- This is of particular importance when using agile in larger projects where these concerns can be overlooked.
Processes need to account for changes in business requirements due to shifting business needs or discovery of misconceptions, reflecting budget cuts in scope changes, and highlighting reductions in scope to meet time or cost constraints.
Projects that push scope into subsequent tranches, even through official change processes, can impact upon delivery confidence.
-
DCA tolerances
-
High
A clear scope with measurable acceptance criteria, aligned to business need, refined through recent consultation with users, suppliers, project team and senior management, including benefits realisation activities. Change is minimal and well controlled.
Off -
Medium high
A clear scope with acceptance criteria aligned to business need, developed through consultation with users, suppliers, project team and senior management, including benefits realisation activities. Change control may be slow to reflect implications of change across project.
Off
Connect with the digital community
Share, build or learn digital experience and skills with training and events, and collaborate with peers across government.