Nano Introduction of Scrum


Hello there,
In today's video, I'm going to talk about the Scrum definition. So, let's dive in.
Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.
Here complex means there are more unknowns than knowns in such problems. So, we need a new way of working, here I mean Scrum.
Scrum is founded based on empiricism and lean thinking.
It uses an iterative, incremental approach.

Scrum brings the following benefits:

  • managing risks,
  • optimizing predictability,
  • validating assumptions frequently,
  • in time adaptation,
  • continuous improvement,
  • continuous stakeholder involvement,
  • and better team morale.

In Scrum, we pick a selection of work for an iteration and create a usable done increment. Then deliver it to stakeholders to get feedback. Based on the feedback, we adapt our next step. Then repeat the process.
Empirical way of working needs three pillars of transparency, inspection, and adaptation. It means using past facts and evidence to make upcoming decisions.
You can compare it with the thermostat's working mechanism.
Hope you enjoyed this video.


Scrum elements are categorized into three categories: Scrum Team, Scrum Events, Scrum Artifacts.
In today's video, I'm going to talk about the Scrum Team.
The fundamental unit of Scrum is a small team of people. A Scrum Team consists of three accountabilities of one Scrum Master, one Product Owner, and Developers.
It is cross-functional and self-managing.
Cross-functionality means that Scrum Team members together have all the required skills to create value in each Sprint.
In addition, self-management means they internally decide who does what, when, and how.
The Scrum Team size is typically 10 or fewer members.
The entire Scrum Team is accountable for creating a valuable and useful Increment every Sprint.

Developers are committed to creating any aspect of a usable Increment each Sprint.

The Product Owner is accountable for maximizing the value of the Scrum Team work.
He or she is also accountable for Product Backlog management.

Scrum Master is accountable for establishing Scrum based on the Scrum Guide.
In addition, is accountable for the Scrum Team's effectiveness.
They are true leaders serving the Scrum Team and the larger organization.
Hope you enjoyed this video.


There are five events in Scrum. Each event is a formal opportunity for inspection and adaptation. In today's video, I'm going to talk about Scrum Events.


Sprint is the heartbeat of Scrum and the container for other events. It is the word that Scrum uses for iteration. Each Sprint is one month at most. The main purpose of Sprint is to create a usable done increment.
Indeed, if we wanted to squeeze Scrum into one sentence, it would be creating done increment.

Sprint Planning

Sprint Planning is an event in which the entire Scrum Team collaboratively creates a plan for the Sprint by inspecting the Product Backlog and other inputs.
Three topics of why, what, and how are addressed in this event. Their answers create the Sprint Backlog.
Its timebox is a maximum of 8 hours for a one-month Sprint and is usually shorter for shorter Sprints.

Daily Scrum

Daily Scrum is a 15-minute event for Developers in which the progress toward the Sprint Goal is inspected and the upcoming work is adapted.

Sprint Review

Sprint Review is an event in which the entire Scrum Team and stakeholders inspect the increment and progress toward the Product Goal and adapt the Product Backlog.
It is a collaborative session seeking feedback and new learning.
Its timebox is a maximum of 4 hours for a one-month Sprint and is usually shorter for shorter Sprints.

Sprint Retrospective

The purpose of the Sprint Retrospective is to find ways to enhance quality and effectiveness.
The entire Scrum Team identifies the most helpful changes to be addressed as soon as possible.
It is an event to focus on continuous improvement by inspecting and adapting individuals, interactions, tools, processes, and finally the Definition of Done.
Its timebox is a maximum of 3 hours for a one-month Sprint and is usually shorter for shorter Sprints.
Hope you enjoyed this video.


In today's video, I'm going to talk about the Scrum Artifacts.

Artifacts represent work or value. They are designed to maximize the transparency of key information.
Each artifact has a commitment which is a new concept that has been introduced in the Scrum Guide 2020. Commitments exist to bring focus and transparency against which progress can be measured.

Product Backlog

Product Backlog is an emergent, ordered list of work necessary for product improvement.
Product Backlog refinement is an activity by which detail is added to the Product Backlog items to have always an actionable Product Backlog.

Product Goal

Product Goal is the future state of the product. You can see it as the long-term objective for the Scrum Team.

Sprint Backlog

Sprint Backlog is composed of the Sprint Goal, forecast, and plan.
It is a highly-visible real-time picture of the work. It is updated throughout the Sprint when more is learned.

Sprint Goal

Sprint Goal is the single objective for the Sprint. It does not change during the Sprint. However, it provides flexibility to negotiate the scope of the work within Sprint if needed. In addition, it brings focus and coherence to the team encouraging them to collaborate together.


Increment is a concrete stepping stone toward the Product Goal.
It brings transparency to the progress, helping the Scrum Team validate its assumptions.
In order to provide value, the Increment should be usable. The work can't be part of the Increment unless it meets the Definition of Done.

Definition of Done

Definition of Done is the formal description of the state of the Increment when it meets the quality measures required for the product.
It increases transparency by bringing a common understanding of what usable and completeness means.

Hope you enjoyed this video.


In today's video, I'm going to talk about the Scrum Values.

You can see the Scrum Values as the spirit of Scrum, which are the five values of Commitment, Focus, Openness, Respect, and Courage.
These values give direction to the Scrum Team with regard to their work, actions, and behavior.
When these values are embodied by the Scrum Team and the people they work with, empiricism comes to life building trust.
Successful use of Scrum depends on the people becoming more proficient in living these values.
It was the last track of the “Nano Introduction of Scrum”. Hope you enjoyed this video series.