guide scrum

Scrum is by far the most widely-used agile methodology in the world.

A free framework that anyone could understand and use in a short period of time, but it might take a long journey of practice to master it. Then you get to taste the real utility of this process framework. It is used to manage products, services, or workflows from the lowest level of complexity to the most hardcore ones. It is based on the continuous improvement of your product, team, and work environment.

Pie chart showing the state of Agile survey.

When you keep those 3 elements on weekly to daily improvement, you’re going to see the magic happening.

First of all, you need to understand 4 things:

 Scrum team

A highly flexible and adaptive small team: The product owner, the development team and a Scrum Master. They work towards the same goal: High level of customer satisfaction, but they have different responsibilities.

Roles

The Scrum Master manages the Scrum process and removes impediments to keep everyone on the right track. The Product Owner manages the Product Backlog and optimizes the value of the product. The development team organizes and manages its own work using cross-functionalities and specialized skills. Everyone plays a complementary role.

Scrum events

  1. Sprint planning (Weekly to monthly 1-9 hours): The Scrum team collaborates, discusses the desired top priority tasks from a larger backlog (to-do list) and defines the Sprint Goal (objective).
  2. Daily scrum (10-15 minutes): an opportunity for the development team to discuss their improvement toward the Sprint goal with the Scrum Master and to make sure everyone is following the right path.
  3. Sprint review (Weekly to Monthly 1-4 hours): The entire Scrum team reviews and discusses what was completed during the Sprint. They also get feedback from stakeholders to make sure they are creating an excellent product.
  4. Sprint Retrospective (Weekly to Monthly 1-3 hours): an opportunity for the Scrum team to inspect last sprint’s activity, to identify and order improved items and finally to create a plan that improves next sprint’s activity.

Scrum artefacts

  1. Product Backlog: A Must-do list of product requirements and features (Responsible: Product Owner).
  2. Sprint Backlog: A product Backlog designed to achieve as many tasks as possible in one sprint (Responsible: Development team).
  3. Product Backlog Item (PBI): a single element from the Product Backlog list.
  4. Burndown chart : Graphic representation of the scrum team’s capacity to end every single PBI on the Product Backlog (Responsible: The Product Owner).

Scrum relies on these artefacts and transparent team communication to achieve optimal value and control risk. The Scrum Team must frequently control scrum artefacts and progress toward the Sprint Goal, it makes easy detecting undesirable variances. The development Team adjusts every aspect of the working processes to reach the Sprint Goal.

The concept of “Done” work or task is strictly transparent for every Scrum Team member, they must have a mutual standard definition of “Done” for each product increment to avoid risks.

As an absolute Scrum beginner, I would recommend everyone having a bad time dealing with a complex project or a boring process routine to understand this lightweight framework and get straight to practice. You won’t regret it. Learn more about the agile methodologies :

JediSquad would be happy to answer any question you might ask or even set up a meeting with you. Don’t be a stranger, just say hello.

MORE YOU KNOW, MORE YOU GROW :

Reading more ? Check out other interesting topics !

WHAT IS THE AARRR FRAMEWORK?THE ARCHERY MOMENTUM FOR AGILE TEAMS
SATISFACTION HISTOGRAM RETROSPECTIVETHE ISHIKAWA MUSEUM AND THE COLLABORATION CONDUCTOR
THE AGILE COACHING CONTRACTHOW TO USE THE TUCKMAN MODEL TO HELP AGILE TEAMS SUCCEED
WHAT IS POKER PLANNING ?EISENHOWER MATRIX: MASTER YOUR TASKS MANAGEMENT
POMODORO : STAY FOCUSED AND DETERMINED !THE BELBIN PRACTICE : GET TO KNOW WELL YOUR TEAMS
THE THREE AMIGOS AGILE PRACTICETHE DECISION-MAKER AND THE CYNEFIN FRAMEWORK
THE SHINING CHANGE CATALYSTPITFALLS OF SPRINT PLANNING
SCRUM BEGINNER’S GUIDEAGILE COACHING RESSOURCES
THE ALCHEMIST AND THE HEART TRANSFORMATION MODELTHE ARTIST OF THE WORKPLACE
THE AGILE GLOBETROTTERONE PERSPECTIVE FROM REAL-LIFE STORIES: WHY A DAILY SCRUM? (EXPLAINED WITH A COMIC)
THE HUMBLE EXECUTIVETHE FIELDWORK ANTHROPOLOGIST
OKR: WHAT YOU NEED TO KNOW TO DEVELOP YOUR BUSINESSMANAGEMENT 3.0: MOVING MOTIVATORS

Related posts

13 thoughts on “SCRUM BEGINNER’S GUIDE”

  1. […] of all, let’s see the key distinctions between a framework (like SAFe per example or Scrum) and a methodology (like XP). This table summarizes everything you need to know about the […]

  2. […] d’abord, voyons les principales distinctions entre un Framework (comme SAFe par exemple ou Scrum) et une méthodologie (comme XP ou Agile). Ce tableau résume tout ce que vous devez savoir sur la […]

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.