Extracts from “2018-19 Lessons Learned Report for ICT-enabled Initiatives”
Published by the State of Queensland (Queensland Health), November 2019
Leadership | Strong leadership is crucial to lay the foundation for success: |
---|---|
Leadership time needs to be invested early to understand what business outcomes are being sought. | |
The level and nature of resources needed must be very deliberately assessed and key senior roles established/acquired/deployed before commencing execution. | |
Sound and clear governance structures and leadership accountabilities must be established. | |
When concerns arise, quick responses are necessary. | |
An agreed future operating model for the transformed business must be developed before solution/vendor selection and development of technology roadmaps. | |
Project management | Correct project management structure, and expertise is required from the very start including the use of appropriate fit-for-purpose, program and project methods. |
Vendor management | Develop a vendor management and relationship strategy as part of initiating the program/project. |
Effective relationships | Devote sufficient leadership resource and time to build effective relationships with internal business customers. |
Scope | Constant attention to the management of scope. |
Governance | Periodic reassessment of governance, leadership and program/project structure arrangements. |
Benefits | Plan early for benefits which includes the transition of ownership to the business. |
Management control:
Lack of defined and/or approved scope | This includes discrepancies in scope definitions amongst key stakeholders and key project artefacts. Key artefacts outlining scope not finalised or approved by the appropriate governance bodies. |
---|---|
Lack of upfront program or project planning | This includes the identification of customer driven products, activities, dependencies and resources needed to inform the schedule and to successfully deliver the program or project business case objectives. |
Lack of/incomplete evidence of transition planning | This includes undeveloped, incomplete, or unapproved support and operating models. There is also evidence of no contractual arrangements with vendors post Go-Live, No BAU support plans, poor articulation of fall- back/contingency plans, and transition to operational governance. |
Lack of defined or adhered to internal controls | Particularly those specific controls that cater for changes when the program or project is forecast to progress outside of approved tolerances. |
Inconsistent development and management - Business Case | Inconsistent program or project business case in terms of clearly defined whole of life program or project costs, benefits and risks. |
Resource management:
Insufficient training and development activities | Training and development activities are inadequate and cannot be operationalised. Further it does not meet the expectations of the end-user cohort. |
---|---|
Lack of clearly articulated roles and responsibilities | Responsibilities are sometimes duplicated, unclear, or overlapping for positions which can lead to potential for conflict in responsibilities being executed. |
Lack of early business engagement | The business and the initiative need to engage fully to get a thorough and early understanding of any requirements for obtaining expertise from the business. |
Unclear operational requirements | The ability to fulfil Business as Usual (BAU) demands should be a prerequisite to business readiness for deployment. Operational requirements need to be well planned and align with the business’s overall capacity. |
Lack of effective resource planning | Resource requirements are not always identified at the outset and that demand, supply and management of resource risks are not included in a resource management strategy or resource plan. |
Recruitment timeframes and processes | Obtaining suitable human resources was identified as a challenge with delays in resource onboarding impacting on additional workloads for existing staff. This subsequently impacted functions and project artefacts. |
Risk management:
Adherence to approved Risk Management Frameworks | Inconsistent and can vary even across an individual project with numerous registers in existence. |
---|---|
Inconsistencies with risk identification | There are inconsistencies noted between risks identified within project documentation such as Business Cases and within the actual project risk registers. |
Systematic and regular reviews of risks andissues | There are inconsistencies noted with whether there are systematic and regular reviews of risks and issues at the initiative level. |
Reporting, review and monitoring of risks | There is limited evidence that the reporting, review and monitoring of risks is occurring consistently at the appropriate governance forums. |
Long-standing risks | Some long-standing risks have been identified that may need to be managed as issues to ensure positive attention and treatment. |