Scrum 101: An Introduction to the World of Scrum Project Management

Who uses Scrum?

Do you know that scrum won’t judge you by your industry? Although the scrum framework was created keeping the software developers in mind, it has nothing to do with your business. Anyone can use this framework to solve complex problems. And that is one of the reasons why scrum is so popular and widely accepted.

The Scrum Master

The scrum master is a servant leader or a project manager who ensures that the execution of the scrum framework is successful. They are responsible for coaching the team to self-organize. The scrum framework has some clear goals and principles. The scrum master makes sure the team is following the principles effectively. Here are some of the responsibilities of a scrum master-

  • Helping the Scrum Team focus on creating high-value Increments that are releasable to the end users
  • Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox
  • The scrum master conducts 1:1 meetings with an individual team member. These 1:1 team interactions are vital for resolving team disagreements and know the areas for improvement.
  • The scrum master helps to analyze the burndown charts to understand the work progress.
  • The scrum master can facilitate change or help remove roadblocks that are harming the team’s progress
  • Facilitating stakeholder collaboration as needed
  • Helps other stakeholders in the organization understand the scrum framework
  • Plans and advises Scrum implementations within the organization;
  • Helps employees and stakeholders understand and enact an empirical approach for complex work
  • Facilitates effective communication between stakeholders and scrum teams.

The Product Owner

The product owner is the voice of the customers. They ensure the customers’ voice is getting heard effectively. A product owner is accountable for maximizing the value by effectively managing the product and product backlog. They determine the priority of the items. The product owner must stay available to the development team to ensure the team gets the clarification they need to be in the right direction. That means they have to return to emails, calls and attend meetings, demos frequently.


Developers are a group of programmers, developers, writers, designers, and everyone who helps to build a usable product with the highest possible quality. Developers primarily have the following characteristics:

  • There is no other title for the developers in scrum. The skills might be different, but everyone is a developer
  • They are cross-functional. They have all the necessary skills required for delivering a working product.
  • They work with a commitment to accomplish the sprint goal every sprint and deliver high-quality products.

A-Z of the Scrum Artifacts

Scrum artifacts are like some vital tools that are needed to achieve a sprint goal. Scrum Artifacts ensure transparency of information.

Product Backlog

A product backlog is a prioritized list that includes all the items your development team needs to deliver a product or make changes. The product owner is responsible for managing the backlog. You can make continuous improvements in the product backlog based on the changes and improvements in the developing product. It is a live document which is refined continuously. The product backlog lists every feature, user story, use cases, bug fixes, and all the improvements that enable any changes to be made in the future release of the product. The developers help the product owner in estimating the items in the backlog.

Sprint Backlog

Sprint backlog includes a list of items that your development team picks from the product backlog to accomplish during the upcoming sprint. The sprint backlog states to the team how much work is needed to achieve the sprint goal. You can maintain the sprint backlog as a spreadsheet. Also, you can use scrum or agile software to manage the sprint backlog. Owned by the developers this also includes a plan that the developers will follow to achieve the sprint goal.

Task Board

User Story

User stories help us to understand a software feature from an end-user view. They help clarify the product user and describe what a user expects from the product and its reason. An example of a typical user story is:

Everything You Need to Know About Scrum Ceremonies

Scrum project management is all about following some organized, time-boxed events, also known as scrum ceremonies. The main purpose of such ceremonies is to help scrum teams develop products effectively without wasting much time.

  • How will the team achieve the sprint goal?

Sprint Planning

During the sprint planning, Chris presents the prioritized product backlog items to the team. Together the team discusses if they have enough equipment, capacity, and everything else to convert these requirements to working software.

  • However, they were unable to finish story 3 as expected. So, it requires more attention and re-factoring.

Sprint Retrospective

After the sprint review meeting, the team again gets together for the sprint retrospective meeting. During the meeting, they discuss what worked well, what did not go well during the sprint and what else they could do to get better in the next sprint. The scrum master takes note of the feedback and acts accordingly to help their team perform better for the second sprint.

Wrapping Up

So, we’re all covered! In this article, you can find all the basics you need to know about Scrum. And, before signing off, let’s remember that the main purpose of scrum is to help you manage your project with its values, events, roles, and artefacts. With its iterative approach, scrum allows you to develop and deliver high-quality products efficiently.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store