The Scrum Values are like a compass guiding us on our journey of using Scrum, while exploring Scrum is a journey in itself. A few weeks back we started the journey of exploring the value of Scrum Values from different perspectives. The journey was inspired by Gunther Verheyen’s post – The Scrum Values. I hope that my exploration of the Scrum Values may guide you in your journey.
1. Commitment
- Developers commit to the Sprint Goal
- Developers commit to adhere to the quality defined as “Done”
- Developers commit to self-organization and collaboration
- Developers commit to uphold transparency so they can regularly inspect their progress and process, and adapt accordingly
- Developers commit to support the Product Owner in updating and refining the Product Backlog
2. Focus
- Developers focus on creating “Done” Increments
- Developers focus on finishing work before starting new work
- Developers focus on preventing and reducing technical debt
- Developers focus on growing their cross-functional capabilities
- Developers focus on team goals rather than individual achievements
3. Openness
- Developers are open about their work, the progress made and the problems encountered
- Developers show openness by collaborating with the Product Owner, the Scrum Master and the Stakeholders
- Developers are open for technical innovation and other ways of continuous improvement
- Developers show openness in managing tensions and conflict in a productive way
- Developers show openness towards emerging work throughout a Sprint that can help them better achieving the Sprint Goal
4. Respect
- Developers respect the ordering of the Product Backlog as decided by the Product Owner
- Developers respect the users by delivering work of high quality and value
- Developers respect stakeholder expectations in terms of regular and reliable delivery
- Developers respect the Scrum Master for suggestions and help offered through a Servant-Leadership approach
- Developers members respect each other’s opinion, skills, expertise and personal backgrounds
5. Courage
- Developers show courage by not delivering undone features in Increments
- Developers show courage by embracing the uncertainty of a complex environment
- Developers show courage by raising impediments to their work
- Developers show courage by incorporating feedback and new insights while creating Increments throughout the Sprint
- Developers show courage by challenging each other and their environment in order to improve
