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 in the city 2017 - Are you Ready to get this Done?"

152 views

Published on

Slides from Agile in the city 2017 session "Are you Ready to get this Done?" (on 15th June 2017)

Published in: Technology
  • Be the first to like this

Agile in the city 2017 - Are you Ready to get this Done?"

  1. 1. Nick Loe-Startup, Holiday Extras Are you Ready to get this Done? @hxtechteam @NickLoe_Startup
  2. 2. Case Study DONE READY DONE’S OK
  3. 3. Kanban>Scrum A brief history of agile at HX
  4. 4. Scrum Training
  5. 5. Putting learning into practice Experimenting Analysing Collaborating
  6. 6. Getting my own Pod to play with Insurance Pod Training Ideas
  7. 7. Defining Done Guidance from the Scrum Alliance
  8. 8. Putting learning into practice Stakeholders Acceptance Criteria Testing
  9. 9. Putting learning into practice Pushing work live Coding Standards Booking Possible
  10. 10. Putting learning into practice CommunicationJira Closed • Task 1 • Subtask A • Subtask B • Task 2 • Subtask C • Subtask D Communication
  11. 11. Putting learning into practice InsightsCommunication Tech Debt
  12. 12. Putting learning into practice MetricsObservation
  13. 13. Streamlining ✓ Checking things are Done
  14. 14. Done as a Web Team A global Done to rule them all
  15. 15. Done as a Web Team Mutually defined Definition of Done
  16. 16. Done as a Web Team Coding Standards Testing Acceptance Criteria Stakeholders Communication Insights
  17. 17. Implementing Done in the Team Planning Marathons
  18. 18. We’re Not Ready Backlog Review with PO Defining Ready Backlog Review Dev Team
  19. 19. What Does Ready Look Like? Discussion Link to Backlog Review
  20. 20. Defintion of Ready What Why How
  21. 21. Spreading the Love Unknowns End User Blockers
  22. 22. Web Team Defintion of Ready End User Blockers Acceptance Criteria Measuring Success Tech Approach Decided Estimated
  23. 23. Keeping things Fresh Adapting to business needs
  24. 24. One Done may not work……. Variation between Scrum Teams
  25. 25. But collaboration brings benefits Business being challenged
  26. 26. Why Done Failed at a Team Level Complicated Who’s Responsible? Who’s Policing
  27. 27. Done by proxy Metrics Observation Stakeholders Acceptance Criteria Testing Coding Standards Pushing Work Live Booking Possible Jira Closed • Task 1 • Subtask A • Subtask B • Task 2 • Subtask C • Subtask D Communication Insights Tech Debt
  28. 28. Too much process Metrics Observation Stakeholders Acceptance Criteria Testing Coding Standards Pushing Work Live Booking Possible Jira Closed • Task 1 • Subtask A • Subtask B • Task 2 • Subtask C • Subtask D Communication Insights Tech Debt
  29. 29. A simple Done and Ready Requirements Reason Acceptance 
 Criteria
  30. 30. Behind the simplicity Acceptance 
 Criteria } Automated Testing Manual Testing Insights / Data Tech approach decided (+ Deployment)
  31. 31. Behind the simplicity Acceptance 
 Criteria } Communication Tech Debt Documentation UXUI & INF consulted where required
  32. 32. Still Keeping it Simple Stakeholders complete part 1 Development Team, part 2
  33. 33. The Future “As Scrum Teams mature…….”
  34. 34. In Summary DONE READY DONE’S OK
  35. 35. Thank You! Any Questions? @hxtechteam @NickLoe_Startup

×