In an earlier blog post I explained some advantages and disadvantages of the "Plan Buy Run" [PBR] model / approach to IT management.
Note: Yes, I know the term is usually "Plan Build Run" - but how many larger organisations these days build everything from scratch
This approach is more "waterfall" in its delivery, which can be effective for organisations that need a clear and structured approach to IT. But it also means they are more subject to the typical issues of:
- Inflexibility: changes made in one phase can have a ripple effect on other phases.
- Delays: as each phase is completed sequentially before the next phase begins, delays earlier one create a shift in the end delivery date
- Lack of innovation: IT is focused on maintaining existing systems and applications rather than introducing new ones.
PDB and agile can run in a hybrid way across the Plan, Buy and also the Run phases.
For example:
- Use agile principles and practices in the planning phase:
This involves business stakeholders in the planning process, creating short-term plans that can be easily changed, and focusing on delivering value to the business. - Use agile methods for building and deploying new IT systems:
This uses iterative and incremental development, working in small teams, and getting feedback from users early and often. - Use agile approaches for operating and maintaining existing IT systems:
This utilises continuous improvement techniques, automating tasks, and responding quickly to changes in business (and especially Non-Functional) requirements.
And ultimately there is no one-size-fits-all approach. The best approach will vary depending on the specific organisation's needs, circumstances and resources.
