When a person says the word “scrum,” people might think they are talking about players in rugby jerseys and standing in a circle, butting heads. But when you bring up Scrum when it comes to the workplace, there is a big chance that you are referencing Scrum with the capital “S”, which begs big the question: “What is the meaning of Scrum? And how can we use it in our work?
What is Scrum?
It is a widely-used agile development plan or a collection of processes, team roles and values used in combination to help create work products. It started in the software world and spread like wildfire in the military, universities, the automobile industry, and other relevant industries.
There is no limit to what kinds of industries that uses this development, and it is an important skill to add to your arsenal when applying for your dream job. But it still leaves a lot of unanswered questions about these frameworks: What does it mean, why is it used, and how does it work? The first step in answering these questions is to discuss its history and origin.
To find out more about hierarchical organization check out https://en.wikipedia.org/wiki/Hierarchical_organization for more details.
Why use the Scrum framework?
According to experts, this strategy is best perceived as an overall approach to issues and avoids rigid and strict specifics, step-by-step instructions. Because people, groups, and projects always evolve and change as time pass by, having one way to do tasks just does not enable growth in an organization. It is the opposite of to-do-lists; it is a new way to approach projects with flexibility.
While this strategy does provide a powerful blueprint for organizing a team, as well as scheduling work, it is a good blueprint that can be formed to help accommodate the need of the company over dictating exactly how they need to proceed.
The difference between Agile Methodology and Scrum
People may have noticed that the definition included the word “agile.” People might also have known about agile methodology. So, are agile methods and Scrum both ways to describe the same thing? Well, to tell you the truth, not exactly. In the ’90s, we saw a movement away from regimented and heavily planned development methodology in the software industry.
More flexible and lighter weight methods, frameworks, and processes began to be used by developers. In the 2000s, a group of developers published and converged Manifesto. According to every Agile coach, while this kind of framework falls within the definition of agile that emerged from the manifesto, not all agile protocols are considered Scrum.
What are Scum principles?
It is defined by a group of values or commonly known as principles that need to be understood as guidelines for working as a team. These are:
Courage during the solving of relevant problems
Commitment to the goal of the company
Respect to every member of the team
Openness about the job, as well as the challenges that the team might face
By embodying the values set by Scrum, teams take on responsibilities for their success and avoid any pitfalls that silo mentality might bring. Unless every member stick to the values, they will not have the right foundation it needs to achieve success. Whether or not the team follows this framework, the values it brings to the team is pretty solid.
How does it work?
The framework is composed of three categories: Artifacts, Roles, and Events.
These are physical records that provide details to the project. Artifacts include Increments, Sprint Backlogs, and Product Backlogs. An increment is the total amount of work completed during Sprints, combined with all the work that was completed during Sprints. The goal is to produce a Done Increment. It is up to the group to agree on what determines the “Done” status, but members need to agree on, as well as understand its definition.
Backlogs are lists of all items from backlogs to be finished during a sprint. The list is put together by making sure that the items from backlogs are prioritized until the team feels they have reached their capacity of Sprint.
A product backlog is the completed and ordered list of every requirements. It acts as a sole reference for the necessary changes.
The framework is defined by three roles: Development Teams, Masters, and Owners.
Development teams are exactly what it sounds like, members working to deliver the product. Despite the word “development” in the title, as well as a software background in Scrum, we need to keep in mind that these things can be anything. Dev teams are given free-reigns when it comes to organizing themselves and manages their work to help maximize the group’s efficiency and effectiveness.
The Masters are the group’s facilitator and responsible for helping members follow theories, practices, and rules. They make sure that they have whatever it needs to help complete the work assigned to them.
Owners are accountable for the work their team needs to complete. Owners are always a single person; while they take inputs from other people when it comes to the decisions they make; the owners have the final say about the project.
Five events mark this framework. Sprints, Retrospective, Reviews, Daily Scrums, and Planning.
Sprints specify the time period during which the group produces their product.
Planning is the meeting where tasks to be done during Sprint is laid down.
Daily Scrums are 15-minute regular meetings where teams have a chance to talk about their tasks and get on the same page, as well as organize a strategy for the day.
Reviews take place after the Sprint ends. During this event, the owner help explain what plans work and what tasks are completed during and after the Sprint. The team will then present a completed task and discuss what is happening and how issues were resolved.
Retrospective takes place after the Sprint. It provides dedicated forums for each team to analyze the process involved during past Sprints and make changes if needed.