Scrum is a lightweight, yet powerful set of practices for managing work. Scrum is a simple model that has its origins in rugby and project management. It’s a transformative approach to delivering valuable software in short iterations with rapid adaptation to change at every step along the way.
The three pillars define the core of what makes Scrum work. They also provide an easy way to remember the Scrum framework and distinguish it from other methods such as Kanban, XP, or even Waterfall. The 3 Pillars Of Scrum: A Practical Guide For Managers: Systemic Coaching It provides a set of rules that guide everything we do in agile project delivery. One critical thing to understand is that the rules aren’t just to be read and understood — they’re there to help you make better decisions. The rules form a stable framework within which people can effectively achieve goals (in this case, delivering valuable software).
In this article, we’ll explain what Scrum is, why businesses need it and how you can put it into practice within your organization. In addition to this, we’ll outline the three pillars of Scrum – transparency, inspection and adaptation – which lie behind its success.
What Is The Origin Of Scrum?
The name “Scrum” comes from a scrummage in rugby. If you’re not a fan of the oval ball game then here’s a quick explanation: two teams push against each other with the aim of pushing an opposing player out of bounds and gaining possession of the ball. Scrum is similar in that it involves competing forces pushing up against one another which leads to movement – but in software development, teams work on problems instead of players.
The team behind Scrum put together these principles for their new approach: embracing change, valuing individuals and interactions over processes and tools, committing to self-organization and focusing on sustainable development. They took these ideas and turned them into something that businesses could use; later they would even go on to create the Certified Scrum Master course.
These days it seems like everyone is a Scrum Master – but not all of them are up to scratch, I tested you with one question from the course and it turned out that you sucked.
The 3 Pillars Of Scrum are:
1. Transparency – completing the sprint goal on a daily basis and making sure everyone can see what is going on.
2. Inspection – involving people in reviewing their own processes, which helps uncover problems that have been around for ages.
3. Adaptation – being agile means being able to react to the changes of your environment, having a process that can handle that is vital.
The Scrum Master has the responsibility of making sure that the team sticks to these 3 pillars. The easiest way to think about it is as a servant-leader role, where the leader helps out the other people on their team instead of just trying to tell them what they should be doing – although that part comes in too. Also the Scrum Master is a facilitator of the process, not a dictator.
What Does a Scrum Master Do?
The most important responsibility of a Scrum Master is making sure that the team abides by the rules and values they have set up in their practice, which includes:
1. Ensures that scrum events take place and are productive.
2. Helps resolve issues with the product being built, if it can’t be fixed at its root cause level then they escalate to the next appropriate person.
3. Helps with establishing standards for each area on the project (eg: design patterns used) and makes sure that everybody sticks to them and uses them correctly (and adds new ones when needed).
4. Ensures that the team is self-organizing and focused on their tasks.
5. Advises the team to stay within the framework of Scrum if they are encountering challenges with completing functionalities in time or if they are falling behind deadlines.
6. Helps to educate others for example how scrum works, what are user stories, what is velocity etc…
7. Ensures that there are no impediments to the team’s progress (eg: poor infrastructure).
8. Recommends solutions for issues faced by other teams working closely with them (eg: design reviews, pair programming sessions etc..)
9. Guides developers during daily scrum so that it can be fast and efficient, sometimes taking over from a developer if they seem to be struggling.
10. Helps with backlog grooming and planning sessions, or acts as a proxy for the product owner when necessary.
11. Oversees sprint reviews and has a good understanding of what is being built so that he can answer questions from stakeholders if necessary.
12. May conduct some exploratory testing during the Sprint to improve product quality while the development team is busy building functionalities / fixing bugs etc…
13. Participates in ATDD sessions (Acceptance Test Driven Development) where possible, documenting test scenarios and writing them in Gherkin language .
Thus ScrumMasters and agile coaches help the team with:
• Effectively using Agile development techniques;
• Removing impediments to development;
• Communicate and encourage cross-functional collaboration and self-organization ;
“It is important to note that a ScrumMaster cannot coach alone – they must work alongside people, e.g. Product Owner, Development Team – and that they must always be working on agreed effective methods.”