Hack 2.0 Lego Agile Workshop
1 like1,130 views
The document outlines an Agile workshop conducted by Reason Digital, focused on building a Lego city or village while applying Agile principles. Key activities include prioritization and estimation of user stories, two eight-minute sprints for building, and retrospectives to evaluate each sprint. The workshop emphasizes iterative working, learning, and the importance of fulfilling user stories based on predefined acceptance criteria.
Hack 2.0 Lego Agile Workshop
- 1. www.reasondigital.com@reasondigital Lego Agile Workshop The Charity Digital Conference
- 2. We’re Reason Digital – a social enterprise that solves the problems that actually matter.
- 4. MVP
- 7. The Lego city & village ● The aim of today’s exercise is to build a Lego city or village using Agile principles ● Each group has a “product vision”, this is there to guide you ● You will have x2 8-minute sprints to build your city
- 8. User Stories ● You’ll see a number of laminated cards on the table that look like this... You need to build something which delivers the user story… ...and meets the acceptance criteria.
- 9. Prioritisation ● Review all the user stories ● These are things you will need to build ● Each of you gets three dots ● Put your dots on the stories which you think are most important
- 10. Estimation Now we need to think about how long each item will take to build 1.Taking each user story in turn, everyone write down how long (in mins) you think it’ll take 1.Based on the results, agree between you on a final estimate Don’t take too long over each one!
- 11. Planning ● Based on the estimation and prioritisation of each user story decide what you’re going to aim to complete in the first sprint
- 12. Sprint 1 You have 8 minutes… GO!!! timer
- 13. Demo Describe what you’ve built to another team. What have you prioritised and why? Do all your user stories pass their acceptance criteria?
- 14. Retro ● Liked - What did you like about the sprint? ● Learned - What did you learn? ● Longed for - What could have gone better? What was missing? What would you like to do differently next time?
- 15. Session 2
- 16. Scrum roles Scrum team Product owner Optimises the value of the product in line with the visionScrum Master Manages the process and team. Removes blockers. Dev team Builds and tests each individual element.
- 17. Dev team roles Dev team Designer Designs each element in- line with the acceptance criteria.Developer Builds the elements based on the designs. Tester Validates that each element works and meets the acceptance criteria.
- 19. Planning Allocate roles out to each member of your team. These should include: ● Product Owner ● Scrum Master ● Designer ● Developer x2 ● Tester You must stick to your roles within the sprint.
- 20. Re-estimation ● How far have you got with your user stories? ● Do you need to re-estimate and replan based on what’s remaining? ● Are there any issue with budget (remaining lego pieces)?
- 21. Planning Based on what you have left to build and what failed your acceptance testing last time, decide what you’re going to aim to build in this sprint.
- 22. Sprint 2 You have 8 minutes… GO!!! timer
- 23. Demo Describe what you’ve built to another team. What have you prioritised and why? Do all your user stories pass their acceptance criteria?
- 24. Retro ● Liked - What did you like about the sprint? ● Learned - What did you learn? ● Longed for - What could have gone better? What was missing? What would you like to do differently next time?
- 25. Wrap up
- 26. Summary ● Prioritisation ● Estimation ● Iterative working ● Learning as you go ● Don’t have to have the full thing finished for it to be valuable
- 27. Further reading ● https://www.gov.uk/service-manual/agile-delivery ● https://www.visual-paradigm.com/scrum/how-scrum-team- works/ ● https://openclassrooms.com/en/courses/4544621-learn-about- agile-project-management-and-scrum/5080926-identify-the- members-of-the-scrum-team ● https://manifesto.co.uk/scrum-roles-scrum-team/ ● https://www.mountaingoatsoftware.com/agile/user-stories
- 28. Extra slides
- 29. Product Vision Each group will need a product vision. They can create this themselves or have a pre-made one. Vision Statement A village / city where... Who is it for? Needs Goals ● Families ● Transport ● Happy citizens
- 30. The charity digital conference 20 November 2019 London #charitydigital Sponsored by
- 31. Visit the CharityComms website to view slides from past events, see what events we have coming up and to check out what else we do: www.charitycomms.org.uk