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

1. Nick Loe-Startup, Holiday Extras
Are you Ready to get this Done?
@hxtechteam @NickLoe_Startup

2. Case Study
DONE READY DONE’S OK

4. Kanban>Scrum
A brief history of agile at HX

5. Scrum Training

6. Putting learning into practice
Experimenting Analysing Collaborating

7. Getting my own Pod to play with
Insurance Pod Training Ideas

8. Defining Done
Guidance from the Scrum Alliance

9. Putting learning into practice
Stakeholders Acceptance
Criteria
Testing

10. Putting learning into practice
Pushing work
live
Coding
Standards
Booking
Possible

11. Putting learning into practice
CommunicationJira Closed
• Task 1
• Subtask A
• Subtask B
• Task 2
• Subtask C
• Subtask D
Communication

12. Putting learning into practice
InsightsCommunication Tech Debt

13. Putting learning into practice
MetricsObservation

14. Streamlining
✓ Checking things are Done

15. Done as a Web Team
A global Done to rule them all

16. Done as a Web Team
Mutually defined Definition of Done

17. Done as a Web Team
Coding
Standards
Testing
Acceptance
Criteria
Stakeholders Communication Insights

18. Implementing Done in the Team
Planning Marathons

19. We’re Not Ready
Backlog Review
with PO
Defining Ready Backlog Review
Dev Team

20. What Does Ready Look Like?
Discussion
Link to
Backlog Review

21. Defintion of Ready
What Why How

22. Spreading the Love
Unknowns End User Blockers

23. Web Team Defintion of Ready
End User Blockers Acceptance
Criteria
Measuring
Success
Tech Approach
Decided
Estimated

24. Keeping things Fresh
Adapting to business needs

25. One Done may not work…….
Variation between Scrum Teams

26. But collaboration brings benefits
Business being challenged

27. Why Done Failed at a Team Level
Complicated Who’s
Responsible?
Who’s
Policing

28. 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

29. 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

30. A simple Done and Ready
Requirements Reason Acceptance
Criteria

31. Behind the simplicity
Acceptance
Criteria
}
Automated Testing
Manual Testing
Insights / Data
Tech approach decided
(+ Deployment)

32. Behind the simplicity
Acceptance
Criteria
}
Communication
Tech Debt
Documentation
UXUI & INF consulted
where required

33. Still Keeping it Simple
Stakeholders
complete part 1
Development
Team, part 2

34. The Future
“As Scrum Teams mature…….”

35. In Summary
DONE READY DONE’S OK

36. Thank You!
Any Questions?
@hxtechteam
@NickLoe_Startup