Appendix F Transitioning to agile, and what constitutes success?
A common mistake made by many organizations is to see working in a more agile way as the goal to be achieved, as opposed to seeing it as an enabler to help the organization achieve its goals. Agile should be seen as a means to an end and not an end in itself.
Organizations and individuals looking to use agile, or improve their agile, should understand the problems they are trying to solve, or the opportunities they are looking to leverage, before commencing on any transition to a new or different way of working.
With respect to ‘traditional’ projects, there are many common problems that are encountered – such as delivering the final product late, being over budget, the solution containing defects or the solution not being what the customer was expecting.
Therefore, when using PRINCE2 and agile together to solve the aforementioned problems and improve how benefits are delivered to internal or external customers, it is important to create a baseline of where the organization currently is, before starting on a journey of transition. From this baseline the organization can set goals to be achieved and create plans to help to achieve them. This can then be used at a future date to see what impact using agile with PRINCE2 has had.