Scrum Practice Part 1
Scrum Practice
This article is an explanation of Scrum in the context that I have used it and what I have discovered. I use the Scrum guide to lay out these topics, give a summary and add my own opinions. If you have not read the Scrum Guide, I highly recommend it. https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf#zoom=100
I have written this to improve my own abilities, please comment and let me know your opinions, thoughts, and feelings so that I can also improve.
** If you see asterisks , this is my recommendations and suggestions from my experiences. I see Scrum as a framework that the team design and work with. With light guidance, they should change and improve and discover how they work best together. In short, it’s your process, feel free to ignore these suggestions and build what works best for you.
Scrum
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. (Schwaber and Sutherland, 2018)
The Scrum framework allows you to use various processes and techniques to improve your product management and how to continuously improve the product, team and the environment you work in. Within this, there are roles, events artifacts, and rules which together bring the value of the framework together. Use this framework where you see fit, not just for software but where a product needs to be developed.
**Scrum is about gaining a cadence with your team through structure and repetition, committing to delivering working software at the end of each iteration called sprints. There are several Events in place to help keep communication between team members high and pushing out to stakeholders the message. Use that feedback to then improve the product and loop around again.
Three Pillars of Scrum
Scrum fundamentally is about making decisions based on previous experiences and what is currently know. Then adapting accordingly by using an iterative and incremental approach. From this, the team can optimise its ability to see predictability and control any risks to the product. From this, there are 3 key pillars to provide this.
Transparency
It is important to be transparent and show all stages of the process so that decisions can be made by those who are responsible for the outcome. A common understanding can be built and will improve implementation of the product
Inspection
Teams need to consciously inspect the processes that they follow. These can be formed using the Scrum Events or feedback methods the team creates, so long as they are not so frequent that it hampers work.
**Sprint Goal is a great way to inspect the teams' process. If there are issues along the way that prevent the team from reaching the goal, record them and discuss them.
Adaption
Use the Scrum Events discussed later for gaining insights on how to adapt the team. If the process is creating problems or work delivered was unacceptable, use these sessions to work with the team on how to improve. Any potential corrections should be implemented in the next iteration to improve the process.
**When considering changes, don’t do everything at once. Roll a few changes one after another to reduce resistance and impact on morale. Constantly changing is almost as bad as no change, people want sustainability and safety. Build out the comfort zone by getting the team used to reflect and improving.
Scrum Values
Commitment, courage, focus, openness, and respect will be the values that Scrum Teams need to live by. For transparency, inspection, and adaption to truly work, the Scrum Team needs to build trust.
To build on these values, the Scrum Team will start to individually commit to the goals and challenges set in front of them. The courage to resolve tough problems and learn from them and to challenge what is asked, not to be afraid to state their point. Focus on the tasks at hand and works towards goals as a team. The Scrum Team and its stakeholder are open about the work, what challenges they face and how they work together to solve the problem. Respect each member of the scrum team and their capabilities.
**Without these values and trust in each other, the Team itself and those around it, Scrum will be extremely difficult to use and will ultimately fail. A team that can’t trust each other shouldn’t work together. It’s really that simple as internal politics and preferences will limit work and progress. If you can, move team members who are playing as team members. One person can drag a whole team down with attitude alone if they really want to.
