Scrum overview
0 likes154 views
The document provides an overview of Scrum, an agile product development framework focused on effective communication, planning, and delivering value through iterative cycles called sprints. It outlines Scrum values such as commitment, openness, respect, and courage, which guide teams in their collaborative processes. Additionally, it describes various Scrum ceremonies designed to facilitate continuous improvement and team alignment throughout the development cycle.
Scrum overview
- 1. Scrum overview Alex Pandel & Michael Torres, 18F In partnership with the Department of the Interior’s Office of Natural Resources Revenue
- 2. Agenda 2 1. What is Scrum? 2. Scrum Values 3. Scrum Ceremonies Scrum overview
- 3. What is Scrum? 3 Product development using Scrum
- 4. Once you have a product vision, and a roadmap, you need some kind of a framework to help you execute 4
- 5. It should do the heavy lifting around communication and planning so that you don’t have to manage that manually 5
- 6. It should also result in continuous, incremental delivery of measurable value 6
- 7. Scrum is one agile product development framework that is designed to do these things 7
- 8. The roots of Scrum lie deep in the concept of Lean as it was first laid out for the Toyota Production System (TPS) and introduced as a software methodology in the 1990s 8
- 9. 1 2 3 4 5Prioritize Scrum delivery cycle Product development using Scrum Plan Build Ship Reflect Team touches base daily to track status and remove blockers
- 10. Scrum is focused on delivering quality software rapidly and in small increments. 10
- 11. It is also focused on breaking down barriers to communication and optimizing for efficiency. 11
- 12. Teams work in time-delimited iterations called sprints. 12
- 13. start end
- 14. Prioritize At the beginning of the sprint, work is scoped at a high level and prioritized into a backlog 14
- 15. P1 P2 P3 to-do
- 16. Plan The prioritized work is then further scoped into small tasks that are grouped together for a sprint 16
- 17. P1 P2 P3 to-do
- 18. P1 P2 P3 to-do
- 19. Build During the sprint, teams work only on those tasks, and check in daily to retain their focus 19
- 20. Build During the sprint, teams work only on those tasks, and check in daily to retain their focus 20
- 21. P1 P2 P3 to-do
- 22. P1 P2 P3 to-do ✔
- 23. P1 P2 P3 to-do ✔ ✔ ✔ ✔
- 24. Ship At the end of the sprint, all delivered work is reviewed and the team decides whether it’s ready to shipped (deployed to production) 24
- 25. P1 P2 P3 to-do ✔ ✔ ✔ ✔ ✔ ✔ ✘ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔✘ ✘ ✘
- 26. P1 P2 P3 to-do ✔ ✔ ✔ ✔ ✔ ✔ ✘ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✘ ✘ ✘
- 27. shipped P1 P2 P3 to-do ✔ ✔ ✔ ✔ ✔ ✔ ✔
- 28. Reflect At the end of the sprint, we take time to reflect on how we can better deliver value to our users, either through process improvements, or responding to feedback. 28
- 29. There are lots of variations in the way Scrum is implemented, but they are all based on a core set of values 29
- 30. Scrum values Product development using Scrum
- 31. Focus
- 32. Scrum enables the team to focus on priorities, so that value is delivered quickly. 32
- 33. We scope work to be small and understandable, so that everyone can align on what to do and why we are doing it. 33
- 34. Commitment
- 35. Commitment is about dedication rather than delivering a specific set of features by a deadline. 35
- 36. We commit to the sprint goal. 36
- 37. We commit to communicating and learning throughout the sprint cycle. 37
- 38. Openness
- 39. Teams need to be open to changing strategies or even goals, as users start to give feedback. 39
- 40. If users tell us we’re not delivering value, we change our strategy or goal accordingly. 40
- 41. Initial value hypothesis ✔Sprint 1 Sprint 3✔Sprint 1
- 42. Initial value hypothesis ✔Sprint 1 ✘Sprint 3 New value hypothesis ✔Sprint 1 Sprint 4
- 43. Respect
- 44. We respect our users and respond to them when something is not working. 44
- 45. We respect our stakeholders by listening and bringing them along. 45
- 46. We respect the role of the product manager to hold the vision, decide on priorities, and drive the team. 46
- 47. We respect the role of designers to advocate for the end user and contribute to the product direction.
- 48. We respect the role of developers to determine the technical implementation and contribute to product direction.
- 49. Courage
- 50. We have the courage to acknowledge that planning does not eliminate change and uncertainty. 50
- 51. We need the courage to speak about our failures so that everyone can learn. 51
- 52. We need to have the courage to change course, sometimes dramatically, when faced with data that contradicts our assumptions. 52
- 53. Scrum ceremonies Product development using Scrum
- 54. Scrum ceremonies Ceremony Phase Backlog refinement Prioritize Sprint planning Plan Daily “stand-up” or “scrum” Build Sprint review / demo Ship Sprint retrospective Reflect
- 55. These ceremonies are designed to move the scrum development cycle along. 55
- 56. They are intended to facilitate communication and planning, so that the team does not have to do this ad-hoc. 56
- 57. They are time-boxed (like sprints) and are dedicated to specific tasks. 57
- 58. Best practices
- 59. Use these meetings for the purpose they were intended so the team can focus on getting through each phase in the development cycle. 59
- 60. Respect the time-box: if you didn’t get to something during the meeting, it likely was not a priority. 60
- 61. Prepare for daily stand-ups by updating the status of your work in your tracking tool (GitHub, Waffle, etc), and identifying your blockers. 61
- 62. Prepare for backlog refinement and sprint planning meetings by reviewing the work in the product backlog prior to the meeting. 62
- 63. Prepare for sprint reviews by making sure you can demo your work to the rest of the team. 63
- 64. Prepare for retrospectives by thinking about how to improve the team’s process, and be open to feedback. 64
- 65. Take turns leading meetings so that no one person is a bottleneck. 65
- 66. Questions?