Assuring agile programmes and projects

Your traditional assurance approach won’t work here

For many organisations, agile methods are beginning to gain ascendancy over traditional waterfall methods as a way to deliver change. With their focus on speed, adaptability, and continuous iteration, agile presents new opportunities for organisations and new challenges for change risk and programme assurance professionals. This has led to a number of misconceptions about assuring agile programmes and projects. Risk practitioners must now evolve their change risk frameworks and mirror the philosophy of agile methods to understand, measure and help mitigate the key risks. The attached thought leadership paper sets out the strategies for overcoming the common myths in agile development and highlights our recommended approach to support organisations navigate this change.

Key highlights

  • Due to the unprecedented level of change organisations and industries are undergoing, agile methods are becoming more prevalent.
  • There are a number of myths to be aware of in relation to agile delivery.
  • What differs between approaches is the development process, including the frequency of delivery, the team structure and organisation of the work.
  • Agile development methods come in a variety of flavours, and although the specifics may differ, the approaches share some common characteristics.
  • When assuring agile programmes and projects, there is a need to think differently— the controls for agile programmes and projects are different because the frequency, evidence, process and governance have changed.
  • The inherent programme/project risks are the same, irrespective of the methodology deployed.
  • If the organisation is working in an iterative way, change risk and programme assurance approaches and recommendations should be iterative and dynamic as well. Flexibility and adaptability are key.
Assuring agile programmes and projects
Did you find this useful?