Scrum in Wonderland Implementing Scrum in Government CoastNerds Group Presentation September 2010
What are we going to talk about
Waterfall
Industry Report Card Source: Standish Group Report 2004
Requirements   use in system Utility of requirement Always used 7% Often used 13% Sometimes used 16% Seldom used 19% Never...
Agile Manifesto Individuals and interactions  That is, while there is value in the items on the right, we value the items ...
Scrum
Scrum
Roles
Ceremonies
Release Planning
Sprint Planning
Daily Scrums What did I do yesterday? What am I going to do today? What is stopping me achieve this?
Sprint Review
Retrospective
Ceremonies Release Plan
Release! Release! Release! Release! Release! Sprinting
Artifacts
Status
In a nutshell…. Source:  scrumforteamsystem.com
The Project
What we delivered <ul><li>A scalable platform </li></ul><ul><li>Enterprise level performance and security </li></ul><ul><l...
Technology <ul><li>.Net 3.5, C#, WPF, WCF,  </li></ul><ul><li>nHibernate </li></ul><ul><li>Sql Server 2005 </li></ul><ul><...
The Facts Trouble Trouble Lines of Code = 106,000 Total Bugs Raised = 103 Bug Rate = 0.1% Industry Standard = 1.5 – 5% One...
Team Values
Evolution Early Middle Late 1 Month Sprints 2 Week Sprints 2 Week Sprints Hour Long Stand-up 15 Minute Stand-up 15 Minute ...
Problem What we did Communication and Trust <ul><li>Broke down team into 3 smaller teams </li></ul><ul><li>Scrum of Scrums...
<ul><li>Test Everything </li></ul><ul><ul><li>Unit </li></ul></ul><ul><ul><li>Integration </li></ul></ul><ul><ul><li>Accep...
Physical   Space
Large to Small Teams
Further Improvements <ul><li>Commit to less but get it all done </li></ul><ul><li>Automated UI Tests </li></ul><ul><li>Man...
Feedback Business Technical Internal External “ Team pulled together” “ Can do everything in AMS” “ Fast turnaround” Appre...
..Finally… <ul><li>Be ready for cultural change </li></ul><ul><li>New levels of trust and transparency </li></ul><ul><li>C...
 
Upcoming SlideShare
Loading in …5
×

Scrum in Wonderland

1,358 views

Published on

Implementing Scrum in Government. A presentation about an 18 month Enterprise project using Scrum and other Agile software development techniques. The team faced many challenges, both on the technical and teamwork fronts, but by the end emerged with a great product and a very high performing team.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,358
On SlideShare
0
From Embeds
0
Number of Embeds
24
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Why are we here? Who are we? The process worked Share our experience and knowledge We had fun
  • Scrum Overview Our Experience over 18 months.
  • Planning Analysis Design Implement Test Support
  • Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas
  • Light weight framework for managing agile projects Concentrate on outcome over activities Force communication Identify issues early Continual Delivery – Motivation Described by Roles, Artifacts and Cermonies
  • Product Owner Responsible for return on investment Customer advocate ROI Product vision Release planning Balances multiple stakeholder views Responsible for requirements and prioritisation Backlog Scrum Master Remove impediments Coach team members and Product owners in their role Facilitate discussions Look for improvement opportunities and tell them to the team Team Ideal size 7 +- 2 Self organising Cross functional – Generalising specialists
  • Same time Same place Pigs and Chickens
  • Product Focused Team, PO, Stakeholder, The World is invited. What team committed to What team achieved Live demonstration Walk through each PBI Feedback -&gt; converted to Product Backlog Items for prioritisation Gain acceptance from Product Owner Any new work
  • Processed Focused What we did well What we didn’t do so well What can we try
  • Product Backlog Item: User Stories As a, I want, so that Acceptance criteria Estimation Priority Non Functional Requirements Try to map to business value Sprint Backlog Item Tasks to meet PBI
  • Estimates? Sprint Burn Down Velocity Product Burn up Release BurnDown
  • Search Business reports Ad-hoc reports Audit and history reports Scalable platform for further expansion
  • Not just the process that got things done The team values We workshopped them
  • Task Board Visibility Co-located Osmosis Workshops in Team Area Short, Focused and Immediate
  • Better Communications Improved Focus Trust and Communication Scrum of Scrums
  • Commitment Over committed Inconsistent Delivery Tech Debt: Aim to not incur any Payback early Reduce unexpected road blocks Product Backlog Groom continuously One source of truth Reduce administrative overhead
  • Scrum in Wonderland

    1. 1. Scrum in Wonderland Implementing Scrum in Government CoastNerds Group Presentation September 2010
    2. 2. What are we going to talk about
    3. 3. Waterfall
    4. 4. Industry Report Card Source: Standish Group Report 2004
    5. 5. Requirements use in system Utility of requirement Always used 7% Often used 13% Sometimes used 16% Seldom used 19% Never used 45% Source: Standish Group study, 2002.
    6. 6. Agile Manifesto Individuals and interactions That is, while there is value in the items on the right, we value the items on the left more We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: processes and tools Working software comprehensive documentation Customer collaboration contract negotiation Responding to change following a plan over over over over
    7. 7. Scrum
    8. 8. Scrum
    9. 9. Roles
    10. 10. Ceremonies
    11. 11. Release Planning
    12. 12. Sprint Planning
    13. 13. Daily Scrums What did I do yesterday? What am I going to do today? What is stopping me achieve this?
    14. 14. Sprint Review
    15. 15. Retrospective
    16. 16. Ceremonies Release Plan
    17. 17. Release! Release! Release! Release! Release! Sprinting
    18. 18. Artifacts
    19. 19. Status
    20. 20. In a nutshell…. Source: scrumforteamsystem.com
    21. 21. The Project
    22. 22. What we delivered <ul><li>A scalable platform </li></ul><ul><li>Enterprise level performance and security </li></ul><ul><li>End to end processing capability </li></ul><ul><li>Standard and ad-hoc reporting </li></ul><ul><li>Interfaces to other systems and business </li></ul><ul><li>Data Migration and cleansing </li></ul>
    23. 23. Technology <ul><li>.Net 3.5, C#, WPF, WCF, </li></ul><ul><li>nHibernate </li></ul><ul><li>Sql Server 2005 </li></ul><ul><li>SSRS </li></ul>
    24. 24. The Facts Trouble Trouble Lines of Code = 106,000 Total Bugs Raised = 103 Bug Rate = 0.1% Industry Standard = 1.5 – 5% One Line Test Code per One Line Production Code. Unit Test Coverage = 75% 14 People 18 Months
    25. 25. Team Values
    26. 26. Evolution Early Middle Late 1 Month Sprints 2 Week Sprints 2 Week Sprints Hour Long Stand-up 15 Minute Stand-up 15 Minute Stand-up 3 Questions Done But Done Done Done Done Done Manual Builds Continual Integration Automate Everything Manual Deployment Scripted Deployment One-click Deployment Poor Estimation Too Much Detail in Estimates Concentrate on Relative Estimates Poor Visibility of Progress Task Boards Whiteboards for Everything Separation Consolidated on Same floor Co-location
    27. 27. Problem What we did Communication and Trust <ul><li>Broke down team into 3 smaller teams </li></ul><ul><li>Scrum of Scrums </li></ul>Quality <ul><li>Definition of Done </li></ul><ul><li>QA Sheets </li></ul><ul><li>Peer Review </li></ul><ul><li>Pair Programming </li></ul><ul><li>Knowledge Sharing </li></ul>Build and Deployment Effort <ul><li>Continual Integration </li></ul><ul><li>Automated Builds </li></ul><ul><li>One-click Deployment </li></ul>
    28. 28. <ul><li>Test Everything </li></ul><ul><ul><li>Unit </li></ul></ul><ul><ul><li>Integration </li></ul></ul><ul><ul><li>Acceptance </li></ul></ul><ul><li>Test Early </li></ul><ul><li>QA Sheet </li></ul><ul><li>Peer Review </li></ul><ul><li>Collaboration </li></ul><ul><li>Sprint Review </li></ul>QA Practices
    29. 29. Physical Space
    30. 30. Large to Small Teams
    31. 31. Further Improvements <ul><li>Commit to less but get it all done </li></ul><ul><li>Automated UI Tests </li></ul><ul><li>Managing Technical Debt </li></ul><ul><li>Product Backlog </li></ul><ul><li>Less Process overhead and paperwork </li></ul>
    32. 32. Feedback Business Technical Internal External “ Team pulled together” “ Can do everything in AMS” “ Fast turnaround” Appreciated opportunity to be involved from the beginning “… use a bit less process…” “… don’t be afraid to make mistakes…” “ ...avoid constraining people…scrum is based on trust...” “ Congratulations, you have one of the few hyperproductive teams in the world. Most companies will not remove their impediments to achieve this.” “ Team is technically awesome” “… great to see so many unit tests…” “… don’t use Entity Framework v1..”
    33. 33. ..Finally… <ul><li>Be ready for cultural change </li></ul><ul><li>New levels of trust and transparency </li></ul><ul><li>Collaboration </li></ul><ul><li>Continual Improvement </li></ul>

    ×