The Scrum Framework and What it Does

Scrum is a framework used within teams to manage highly uncertain projects. This framework helps people tackle adaptive, complex problems while delivering highly valuable and creative projects. Scrum is simple and easy to understand; however, it can be difficult to fully master. This framework favors time to market and the quick delivery of MVP (minimum viable projects). 

What is the Origin of Scrum? 

In 2001 in Salt Lake City, a group of developers led by software engineer Kent Beck met to share their frustrations about software delivery methodologies and the frameworks that existed then (PMI, CMMI, or SPICE). The Agile Manifesto came from this meeting and its goals can be summed up in the following four values: 

• Value individuals and their interactions above processes and tools 
• Value software that works above exhaustive documentation
• Value client collaboration above contractual negotiation 
• Value response to change above following a plan 

The 12 Principles of the Agile Manifesto 

In addition to the previously mentioned 4 values, signers of the Agile Manifesto highlighted 12 principles that came from it and which are equally important: 

1. Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity–the art of maximizing the amount of work not done–is essential.
11. The best architectures, requirements, and designs emerge from self-managing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

The 5 Values of Scrum 

The Agile Manifesto and Scrum go hand-in-hand to offer a clear guide to development teams when facing a new project. This means that there’s a series of values associated with the Scrum framework that should be kept in mind: 

• Courage: have the courage to do the right thing and work on tough problems
• Focus: the organization of tasks in sprints provides certainty and allows us to focus on attainable goals
• Commitment: for the Scrum framework to be successful, the entire team must be committed
• Openness: the Scrum team must be transparent about work and obstacles 
• Respect: team members must treat each other with respect, valuing the ideas and efforts of each person

What is the Scrum Framework Based On? 

As it falls within the agile methodologies, Scrum is based on aspects like: 

• Flexibility for adapting to change and new requirements during a complex project
• The human factor
• Collaboration and interaction with the client
• Iterative development as a way of ensuring good results

The most important pillars or characteristics of the Scrum framework are: 

1. Transparency: With the Scrum framework, all involved are aware of what is happening in the project and how it happens. This creates a common understanding and global vision of the project.
2. Inspection: The members of the Scrum team frequently inspect progress to detect possible problems. The inspection isn’t a daily test, but instead a way to ensure that the project is functioning properly and that the team is self-organizing. 
3. Adaptation: When there’s something to change, the team adjusts to achieve the goal of the sprint. This is key to reaching success in complex projects, where requirements are changing or loosely defined and where adaptation, innovation, complexity, and flexibility are key. 

Roles in the Scrum Team 

If we follow the Scrum values and principles, the team has to focus on delivering value and offering high-quality results that allow the client to meet their business goals. 

That’s why Scrum teams are self-sufficient and multifunctional. This means that each person is responsible for finishing certain tasks in established time periods. This guarantees the entire team’s deliveries, without needing the help or detailed supervision of other organization members. 

Here are the three most important roles on a Scrum team: 

Product Owner

The Product Owner is responsible for maximizing the value of the development team. Maximizing the value of the work goes hand-in-hand with the proper management of Product Backlog, which we’ll explain later on. 

This is the only role that is in constant contact with the client, which requires them to have a lot of knowledge about the business. 

Lastly, a Scrum team must have just one Product Owner; they can be part of the development team. 

Scrum Master

The Scrum Master is responsible for ensuring that the Scrum techniques are correctly understood and applied in the organization. As the Scrum Master, they are in charge of eliminating any problems or issues that a team has within a sprint (that will be further reviewed later on), applying the best techniques to strengthen the digital marketing team. 

Within the organization, the Scrum Master’s role is to help all teams adopt the framework.

Development Team 

This team is in charge of realizing the prioritized tasks of the Product Owner. It’s a multifunctional and self-managed team; they are the only ones that can estimate backlog tasks without outside influence.

Development teams don’t have sub-teams or specialists. The goal is to share the responsibility if someone can’t finish all the tasks of a sprint. 

Scrum Team Events

This chart reflects the different Scrum ceremonies and their weight, according to different weeks. Iterative development is realized in a sprint that contains the following Scrum events: Sprint Planning, Daily Meeting, Sprint Review, Sprint Retrospective, and Grooming. 

Before diving deeper into the different events, it’s important to define what a Scrum sprint is. The sprint is the heart of this framework, the container of the other parts of the process. Everything that happens in an iteration to deliver value is within a sprint; the maximum length is one month and this duration is determined based on the level of communication that the client wants to have with the team. Long sprints can mean that valuable client feedback is lost and puts the project in danger. 

Sprint Planning

In this meeting, the entire Scrum team will define what tasks they will undertake and the goal of the sprint. The first meeting of a sprint can be up to 8 hours for a one month sprint. 

The team will ask the following questions: 

• What will we do in the sprint? We will choose the Product Backlog tasks based on this. 
• How will we do it? The development team will define the necessary tasks to complete each chosen item of the Product Backlog. 

The definition of what will be done gives the team a goal and makes them committed to the valuable deliverable that will be given to the client at the end of the sprint. This is called the Sprint Goal. 

The result of the meeting is the Sprint Goal and a Sprint Backlog (which we’ll cover later on). 

Daily Meeting

This is a daily meeting within the sprint that lasts a maximum of 15 minutes. The development team and the Scrum Master must attend this meeting no matter what; the Product Owner doesn’t need to be present. 

In this daily meeting, the development team will ask the following three questions:

• What did I do yesterday?
• What am I going to do today?
• Do I have any issues that I need to solve? 

A Daily Scrum is the best place to be able to inspect completed work and adapt in case the sprint tasks have changed. 

Sprint Review 

The value review that we will deliver to the client will happen in this meeting, which takes place at the end of each sprint. For one month sprints, it will last four hours and is the only Scrum meeting that the client may attend. 

In this meeting, the Product Owner presents developments to the client and the team presents its work. The client validates the realized changes and, in addition, provides feedback about new tasks that the Product Owner will have to add to the Product Backlog.

Sprint Retrospective

The retrospective is the last Scrum event, lasts three hours for one month sprints, and is the team meeting in which the evaluation of the Scrum framework’s implementation in the latest sprint will be carried out. 

It’s a great opportunity for the Scrum team to self-reflect, proposing improvements for the next sprint. The end result is a list of improvements to be applied the next day, given that once the retrospective is completed, the next sprint immediately starts, which includes the same events that were previously mentioned. 

Grooming

Scrum Grooming is the revision time dedicated within teams during sprints to touch-up its requirements. It’s a meeting that cannot occupy more than 10% of the sprint’s available time. The user’s tasks will be revised with a few advantage sprints so that once the team arrives, everything is ready for task development. 

Scrum Artifacts

Scrum events and artifacts are defined to fully maximize transparency within the team; this means that everyone will have the same vision of what is happening in the project. 

If you’re asking yourself what Scrum artifacts are, we’ll explain the 3 key aspects: Product Backlog, Sprint Backlog, and Increment. 

Product Backlog

Product Backlog is basically a list of tasks that captures an entire project. Anything that we have to do must be in the Product Backlog with an estimated time for the development team. 

The responsibility of organizing the Product Backlog lies exclusively with the Product Owner, which is why they must be in contact communication with the client to ensure that priorities are properly established and the highest tasks are of a greater priority. The development team chooses tasks from the Product Backlog in the Sprint Planning to create both the Sprint Backlog and the Sprint Goal. 

Sprint Backlog

This is the group of tasks from the Product Backlog that the development team chooses in Sprint Planning together with their development plan. It must be known by the whole team, to ensure that the focus should be on that task group. 

Sprint Planning doesn’t change during the sprint; only the plan can be changed to be able to develop them. 

Increment

The Product Increment or Scrum Increment is the result of combining all the elements of the Product Backlog that were completed during the actual sprint and also adding the value of all previous sprints. 

The sum of the increments are presented in each Sprint Review and various Scrum increments can be created within the same sprint. 

Advantages and Disadvantages of the Scrum Framework 

Once we know how Scrum works, we can talk about its advantages and disadvantages: 

Advantages of the Scrum Methodology 

• Scrum is easy to learn: the roles, hits, and artifacts are clear and have a goal, which makes it a methodology that’s related closely to our daily way of working.
• The client can quickly begin to use the product.
• The process is easier, given that there is frequent delivery.
• There’s less chance of surprises or problems because the client is frequently viewing the project.

Disadvantages of the Scrum Methodology 

• Although Scrum is easy to learn, it’s very hard to implement. It requires a certain attitude and change in organizational culture that goes from managers to the client.
• The need to have multidisciplinary teams can be a problem, given that it’s hard to find people who are capable of doing an entire team’s work.
• The team can tend to take the shortest path to achieve sprint goals, which doesn’t always offer quality results. 

To sum it up, the Scrum methodology is especially useful when working in highly uncertain environments, in those when the probability is high that there are changes in the program. If these requirements aren’t clear and if the client needs to quickly release a product in the market or needs an MVP, Scrum is the perfect framework. This framework allows us to deliver a product in various working and independent parts at a quick pace and with the ability to correct errors in the moment. 

At We Are Marketing, various members of our development team are certified as Scrum Masters. We possess the knowledge and necessary tools to successfully complete projects using this framework and we offer clients visibility and control over our actions. Scrum embraces change; if you’re looking for an agile team that clearly understands this, you can trust We Are Marketing.