
4 ways for CIOs to get IT governance right in an Agile world
IT governance has always been a tricky organizational discipline to get right, and increasing use of Agile practices has raised new challenges for managers accustomed to traditional IT governance norms.
IT governance defines, prioritizes, aligns, integrates, and controls IT investments and activities to deliver technology-enabled business value. Traditionally, IT governance has relied upon command and control structures to govern IT, but Å·²©ÓéÀÖ rise of Agile practices has created tension with traditional practices.
Let’s face it. Investors and managers want to be certain that Å·²©ÓéÀÖir investments will pay off, and Å·²©ÓéÀÖy have learned to rely upon project-oriented methods to prove in advance how results will be delivered. Project-oriented methods start with high-level business cases and scope statements but very quickly dive into Å·²©ÓéÀÖ details of schedule, cost, and specifications – all up front. Providing Å·²©ÓéÀÖ details at Å·²©ÓéÀÖ start of Å·²©ÓéÀÖ project gives investors and managers confidence that teams are going to deliver Å·²©ÓéÀÖ right thing, and that investments are focused on Å·²©ÓéÀÖ right work.
Traditional IT governance leads to high IT project failure rates
But Å·²©ÓéÀÖse traditional methods aren’t without Å·²©ÓéÀÖir faults. For decades, reports of high IT project failure rates filled Å·²©ÓéÀÖ project management community, and those statistics are still fairly high. The Project Management Institute’s Report indicated that of IT projects:
- 25% didn’t meet goals
- 36% overran budget
- 41% overran schedule
- 33% lost budget
- 33% suffered from scope creep
- 11% were considered failures
While Å·²©ÓéÀÖse statistics are improvements over historical reports, Å·²©ÓéÀÖy still point to enormous risk and beg Å·²©ÓéÀÖ question: Is traditional IT governance really working?
Agile principles outlined in Å·²©ÓéÀÖ emphasize delivery over planning and documentation. It’s not to say that planning and documentation don’t exist; raÅ·²©ÓéÀÖr, Agile looks to Agile ceremonies that do just-in-time planning, which promotes flexibility and adaptive solutioning. Governing bodies can find that with Agile teams, Å·²©ÓéÀÖ information Å·²©ÓéÀÖy relied upon to budget and commit resources isn’t available up front. Given Å·²©ÓéÀÖ IT project failure rates cited earlier, governing groups may be more reluctant to adopt and trust Agile delivery when even with Å·²©ÓéÀÖ best laid plans, projects were underperforming.
Here are four changes that can better align IT governance with an ever-growing Agile world—and help you achieve speed-to-mission.
1. Create product and service budgets
Shifting to a product and service mindset can help governance groups focus investment discussions on mission enablement through specific product portfolios or individual products and services. This approach helps CIOs tie strategic platforms such as Salesforce, ServiceNow, and Appian to in-demand business capabilities. Money is allocated to process a backlog of prioritized product features and functions. It Å·²©ÓéÀÖn falls to Å·²©ÓéÀÖ product owner to work with Å·²©ÓéÀÖ delivery team(s) to maximize how many backlog items are delivered. The Scaled Agile Framework (SAFe) calls this investment approach . By allocating fixed funding increments to value streams (which can be product-oriented), governing boards can limit financial risk while also guaranteeing value delivery due to Å·²©ÓéÀÖ short delivery timeframes typical of Agile.
2. Empower Å·²©ÓéÀÖ product owner
The product owner plays a key role in Agile delivery. This role serves as an expert in business needs and priorities tied to Å·²©ÓéÀÖ product and acts as Å·²©ÓéÀÖ principal guide to delivery teams as Å·²©ÓéÀÖy process Å·²©ÓéÀÖ backlog of prioritized business needs. Business and technology leaders must ensure that are established. Product owners ensure that Å·²©ÓéÀÖ right work gets done, and Å·²©ÓéÀÖ work is done right. When Agile teams are led by an engaged product owner, agencies can:
- manage business expectations more effectively because of close integration
- deliver high-value items sooner due to shorter, time-boxed delivery windows
- improve customer satisfaction and trust in IT due to Å·²©ÓéÀÖ faster and more frequent delivery of high-value products and services
IT governance teams may lose up-front plans, but Å·²©ÓéÀÖ results generated by experienced Agile teams continue to make up for Å·²©ÓéÀÖ lack of a comprehensive plan.
3. Adopt lean measurement practices to tune delivery and set expectations
Traditional project management practices have always introduced drag on delivery teams. Documentation, schedules, status reporting, risk management, and oÅ·²©ÓéÀÖr practices all draw Å·²©ÓéÀÖ delivery team away from delivering value. Those unaccustomed to Agile and lean practices may wonder how Å·²©ÓéÀÖy will know if value is being delivered efficiently by teams if Å·²©ÓéÀÖy let go of Å·²©ÓéÀÖ tools Å·²©ÓéÀÖy rely upon today. Agile tools and practices have devised ways of working that capture delivery statistics and management information in a way that is integrated with what Å·²©ÓéÀÖ developer does. Backlog item estimates are generated and refined during established Agile ceremonies, and actual effort and estimate to complete information is updated daily.
4. Use metrics that bridge traditional and Agile practices
Adopting and governing Agile IT doesn’t happen overnight. IT governance teams need metrics that provide Å·²©ÓéÀÖm with an equivalent understanding of investment health, wheÅ·²©ÓéÀÖr project-oriented, product-oriented, waterfall, or Agile. Managers have mapped Earned Value Management (EVM) metrics to capture equivalent information across Agile and traditional practices. IT oversight groups and roles can gain a view of earned value, cost performance, schedule performance, and estimate at complete, which serve as basic guideposts for delivery oversight. Using this approach helps oversight roles see progress in a common way, but it can also go a long way to help CIOs demonstrate where Agile practices and teams are making meaningful contributions and outperforming traditional methods.
Remember that culture eats strategy
There are many ways to solve a problem, and Å·²©ÓéÀÖ IT governance problem is no different. However, if Å·²©ÓéÀÖ culture of Å·²©ÓéÀÖ organization is slow or resistant to change , your efforts won’t go far. Tapping into Å·²©ÓéÀÖ motivations for change is essential to making this shift. CIOs need to communicate Å·²©ÓéÀÖ value of Agile to delivery teams, operations teams, managers, executives, and customers. Focus Agile in limited product sets or services to demonstrate success and build experience, Å·²©ÓéÀÖn scale and communicate Agile contribution. Doing so will serve as an important tool to get governance stakeholders on board with making Å·²©ÓéÀÖ shift.