1 / 32

Chaos and Collaboration A Successful Adoption of Scrum by a Government Department

Chaos and Collaboration A Successful Adoption of Scrum by a Government Department. Pete George George Training & Development Ltd www.GeorgeTD.com.

nay
Download Presentation

Chaos and Collaboration A Successful Adoption of Scrum by a Government Department

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chaos and CollaborationA Successful Adoption of Scrum by a Government Department Pete George George Training & Development Ltd www.GeorgeTD.com

  2. “Almost exactly a year ago I set you the challenge of delivering a … capability … You successfully met this challenge and delivered us a significant new capability in July. Since then, the capability has been used to support a large number of … operations, a number of which have represented major gains for HMG … It’s been a fantastic 7 months … we couldn’t have done it without you!” Extract from a letter by the Deputy Director of a large HMG department, Jan 2010

  3. The Challenge APP1 APP2 APP3 APP4 APP5 APP6 APP7 APP8

  4. The Answer??

  5. “[Scrum] was a breath of fresh air really. It helped us clear the deadwood out of our processes and practices, which we’d adhered to ‘slavishly’. It gave us a clear connection to users” Technical Architect, Blazing Saddles Team

  6. 2005 – Customer Wanted

  7. 2005 - Construction 2006 - Construction 2007 - Construction 2008 - Construction

  8. 2008 - Customer Got

  9. 2008 - Customer Finally Got

  10. 2008 - Customer Wanted

  11. The Conclusion APP1 APP3 APP2

  12. Scrum Artefacts Product Backlog Sprint Backlog Product Increment Burndown Chart Sprint Release Period

  13. Scrum Artefacts Product Backlog Sprint Backlog Product Increment Burndown Chart Sprint Release Period

  14. Scrum Roles Scrum Master The Team Product Owner

  15. BzS Product Owner • Saw Team’s problems first-hand • Relegated Backlog items • Managed users’ expectations • Focused Team on completing applications • Ensured most important applications delivered • Collaborated on estimates for post-July work

  16. BzS Product Owner • Saw Team’s problems first-hand • Relegated Backlog items • Managed users’ expectations • Focused Team on completing applications • Ensured most important applications delivered • Collaborated on estimates for post-July work

  17. Scrum Ceremonies Product Backlog Prioritisation Daily Scrum Review/Demo Sprint Backlog Planning Retrospective Sprint

  18. Scrum Ceremonies Product Backlog Prioritisation Daily Scrum Review/Demo Sprint Backlog Planning Retrospective Sprint

  19. “One of the best things I found was the close working with the principal users, having them present in the daily stand up was a boon in sanity checking our understanding of requirements and also to get ‘micro priority judgements’…It was a satisfying way of working because of the continuous feedback.” Developer, Blazing Saddles Team

  20. “[the user community] always had something constructive to add and it made it seem to me that they were delivering a ‘buy in’ to the Product.” Tester, Blazing Saddles Team

  21. Increased Collaboration • Demonstration feedback • Test charters • Pair-based exploratory testing • Alpha testing • Beta testing

  22. Increased Collaboration • Demonstration feedback • Test charters • Pair-based exploratory testing • Alpha testing • Beta testing

  23. Chaos? • Technical Debt • Support Costs • Practices not principles • Culture shock within Team • Conflicting methodologies across the organisation • No time for Retrospectives

  24. Chaos? • Technical Debt • Support Costs • Practices not principles • Culture shock within Team • Conflicting methodologies across the organisation • No time for Retrospectives

  25. Chaos? • Technical Debt • Support Costs • Practices not principles • Culture shock within Team • Conflicting methodologies across the organisation • No time for Retrospectives

  26. What Success Looks Like

  27. Agile TeamHealth Check A Workshop for Agile Teams Who Are Still Improving www.georgetd.com

  28. Agile Team Health Check The Health Check is a half-day workshop for any team (max 20 members) who would like to improve their current way of working with the help of an experienced Agile facilitator. George T&D will provide the facilitator. All you need to do is provide a suitable venue (and coffee!). The workshop consists of a series of group exercises designed to help the team reflect together on how they are currently operating in the light of the 12 Agile Principles, and how they can perform better. Schedule 09:00 Who are we? Introductions and team exercise 09:45 Why Agile? Agile Principles review exercise 10:45 Coffee break Coffee break 11:00 How are we doing? Retrospective exercise 12:00 Where are we going? Action brainstorm exercise 12:30 Finish For more details or to book the workshop, email: enquiries@georgetd.com

More Related