Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile governance presentation

4,000 views

Published on

In some agile circles, ‘governance’ is almost a dirty word. To many, it means bureaucracy, documentation, heavyweight process and a lot of wasted time and effort. And in a lot of cases, that’s how it is. But equally, a lot of companies today operate in a complex and highly regulated environment and they are delivering their change portfolio through projects that require some form of control to ensure their success. Traditional approaches to governance through documentation and RAG status are not compatible with agile. And blaming any and all failures on the project manager – or the Scrum Master - is naïve and irresponsible.

So how do companies run their portfolio of agile projects in a way that ensures adequate oversight without stifling the agility?

This talk presents a framework of 8 principles, two roles and one key practice that will not only achieve that, but can also be a catalyst for agile improvement across the portfolio.

Published in: Software
  • Tired of being scammed? Take advantage of a program that, actually makes you money! ▲▲▲ http://scamcb.com/ezpayjobs/pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile governance presentation

  1. 1. Principles of Effective Agile Project Governance Building an effective Enterprise Governance model Chris Davies @aterny www.aterny.co.uk
  2. 2. So… Governance? 2© ATERNY Agile Services
  3. 3. What do you believe? 3© ATERNY Agile Services Governance is essential for all projects in one way or another Governance is not applicable in an Agile environment
  4. 4. The Project Manager 4© ATERNY Agile Services
  5. 5. Regulations & Standards 5© ATERNY Agile Services
  6. 6. Why Govern? • Ensures strategic alignment of IT with the business • Minimise the risk of bad outcomes 6  Business-driven pipeline  Project vision aligned with corporate strategy  Vision clear to all  Outcome-based metrics  Iterative demonstrations  Continuous improvement  Stable teams  Roles and responsibilities  Professional discipline  Active involvement  Firm Foundations  Iterative development, integrated testing  Early, incremental delivery  Requirement prioritisation  Responsive to change © ATERNY Agile Services
  7. 7. Does Agile need governing? 7© ATERNY Agile Services
  8. 8. Agile Projects Fail too 8© ATERNY Agile Services
  9. 9. Characteristics Of Bad Governance • Document-driven • Autocratic • Process heavy • Subjective • Inefficient • Often ineffective Of Good Governance • Consensus-driven • Equitable & Inclusive • Transparent • Objective • Efficient • Effective 9© ATERNY Agile Services “Trust, but Verify”
  10. 10. The Framework 10© ATERNY Agile Services 8 Principles 1 Governor Virtual Governance Authority 3 Checkpoints
  11. 11. The 8 Principles 11© ATERNY Agile Services Appropriate Accountability Resource Projects adequately Scale the Governance Ensure Adequate Contingency Planning Throughout Transparency of Process & Progress Outcome-based Reporting Review Viability Frequently
  12. 12. 1. Appropriate Accountability • Professional Accountability • Who cares?? The Virtual Governance Authority under one Governor 12© ATERNY Agile Services PMO?IT Security Enterprise Architecture Finance Compliance Infrastructure Marketing Production Support
  13. 13. 2. Resource Projects adequately • Commitment vs “giving it a go” • Ensure reasonable chance of success 13© ATERNY Agile Services • Stable teams • Cross-functional • Active Business Involvement • All required skills
  14. 14. 3. Scale the Governance “That governance is best that governs best with least.” Eric Marks, CEO of AgilePath Corporation • Self-scaling • Event-driven • Virtual Group – Not static – No regular meetings 14© ATERNY Agile Services
  15. 15. 4. Ensure adequate contingency • Realistic contingency – time, cost, or features? 15© ATERNY Agile Services Traditional Agile
  16. 16. 5. Planning throughout • ‘Just enough’ planning • Are plans sensible? 16© ATERNY Agile Services
  17. 17. 6. Transparency 17© ATERNY Agile Services Process and progress Tools for remote collaboration VGA members attend
  18. 18. 7. Outcome-based reporting • Beware an ‘alternate reality’ • Report value delivered, not effort or activity • Consider the source • The convenience of iterations and user stories 18© ATERNY Agile Services 33 33 33 33 33 35 45 45 45 45 45 64 85 85 85 65 63 27 163 163 163 143 141 126 0 5 10 15 20 25 0 20 40 60 80 100 120 140 160 180 Start Sprint1 Sprint2 Sprint3 Sprint4 Sprint5 Sprint6 Sprint7 Sprint8 Sprint9 Project Progress Won't Could Should Must Burndown Velocity Linear (Burndown) 0 20 40 60 80 100 120 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 StoryPoints Days Cumulative Flow Complete Testing Complete In Testing Ready For Testing In Development
  19. 19. 8. Review viability frequently • Project environment is rarely stable • Are success factors still in place? – People – Scope – Design – New constraints • Use Agile cadence for checkpoints • Role of the VGA – question, challenge, assist 19© ATERNY Agile Services
  20. 20. Governance Checkpoints 20© ATERNY Agile Services
  21. 21. How Checkpoints work • 30-minute audio-conference • Governor asks questions of the VGA • Checklist based, e.g. 21© ATERNY Agile Services Feasibility • All • Architecture • Business Sponsor • All • Is the business problem understood? • Is there a viable solution? • Is there a business case for this? • Stop or Go? Foundations • Product Owner • Architecture • IT Security • Compliance • All • Has the breadth of scope been captured? • Have you cleared the technical design? • Are security requirements captured? • Are regulatory requirements captured? • Is the Release plan sensible? Deployment • Product Owner • Architecture • IT Security • Customer Support • Satisfied with the value and quality? • Solution complies with roadmap? • Solution tested as secure? • Have staff been trained?
  22. 22. Building the model “People and Interactions over Processes and Tools” 22© ATERNY Agile Services Identify Governor and the VGA Create Checklists Schedule Checkpoints Collect Metrics Publish the model Review the model Embed the process
  23. 23. The Agile PMO 23© ATERNY Agile Services Team Remove Impediments Facilitation Training & Coaching Portfolio Dependencies Help Business integrate Maintain MI, reporting Transformation Tracking Reporting
  24. 24. Conclusion Agile is collaborative and iterative Agile Governance should be too 24© ATERNY Agile Services
  25. 25. Contact me Email Chris@aterny.co.uk www.aterny.co.uk www.twitter.com/aterny 25© ATERNY Agile Services • Agile Training • Agile Coaching • Transformation Consultancy

×