Introduction to Scrum: What, How, and Why – Webinar by Serhii Riabtsev

On September 24, Serhii Riabtsev, a Scrum Master at Daxx Kyiv, gave an insightful online lecture to Daxxers “Introduction to Scrum: What, How, and Why.” Serhii made a great introduction to the subject of Scrum and Agile, explained the difference between them, and presented the main concepts. Find the key takeaways below!

Let’s take a closer look at some definitions and terminology. It would be a good idea to start by clearing up the biggest misconception regarding Agile and Scrum. They are NOT the same concepts. So, what’s the key difference between them?


Never confuse Agile with Scrum. Agile is a methodology, a mindset, a philosophy focused on communication, team-thinking, flow, and value creation while developing a product. It’s a broad concept. Scrum is an Agile framework for handling roles, events, artifacts, and rules/guidelines to implement the Agile mindset. In short, Agile vs. Scrum = Methodology vs. Framework.

The term ‘Scrum’ was coined in 1986. Hirotaka Takeuchi and Ikujiro Nonaka introduced it in the context of product development in their Harvard Business Review article in 1986, ‘The New New Product Development Game’. In the early 1990s, Ken Schwaber used what would become Scrum at his company.


 I. Roles

1.1 Product Owner

A Role, which has a clear business view on the product – what and why should be done to approach a goal. Could have a non-technical mind, still working close with the Development Team

1.2 Development Team

It is a group of persons, who literally creates the working product through iterations. It consists of developers, designers, QF, etc. They all act as one cross-functional unit, ready to react to any changes and blockers.

1.3 Scrum Master

A leader-servant role. This person facilitates necessary actions within the team, removes outer blockers and solves inner conflicts. Also, he is responsible for keeping Scrum values, philosophy and actions functional, spreading the influence to the whole organization.

All these three roles complete a Scrum Team, who is responsible before the Stakeholders for the Product completion, support and further development.

II. Meetings

2.1 Daily Scrum

Traditionally, daily Scrum meetings last for 15 minutes. Scrum Master ensures that the Development Team has the meeting. However, the Development Team members are responsible for conducting daily Scrum meetings. Product owner, however, could skip it. 

2.2 Sprint Planning

A mandatory meeting for the Scrum Team which has its goal to choose what items from the Product Backlog should be done to reach Sprint Goal and complete the Sprint Backlog.

2.3 Sprint Review

Here Scrum Team reviews the work that was completed and the planned work that was not completed. Also, a Demo for the Stakeholders could take place. 

2.4 Sprint Retrospective

A chance for the Scrum Team to inspect itself, find all goods and bads and decide how to avoid blockers and keep benefits in the upcoming Sprints.

Also, a so-called Backlog refinement could be done in case there are any misunderstandings or out-to-date items within Product Backlog

III. Artifacts

3.1 Product Backlog

Contains a list of items that should be done by a Scrum Team to complete the Product. As the Product grows, the Product Backlog is growing too, so it is never complete and should exist as long, as the Product itself. 

3.2 Sprint Backlog

A smaller items list, consisting of reviewed, prioritized and estimated Product Backlog items for the Development Team to complete during the Sprint. 

3.3 Increment

The Increment is the potentially releasable output of the Sprint that meets the Sprint Goal. It is formed from all the completed Sprint Backlog items, integrated with the work of all previous Sprints.


  • Commitment: Team members individually commit to achieving their team goals, each and every sprint.
  • Courage: Team members know they have the courage to work through conflict and challenges together so that they can do the right thing.
  • Focus: Team members focus exclusively on their team goals and the sprint backlog; there should be no work done other than through their backlog.
  • Openness: Team members and their stakeholders agree to be transparent about their work and any challenges they face.
  • Respect: Team members respect each other to be technically capable and to work with good intent.

To sum up, Scrum is a complex and deep structure to be explored. The information, Serhii has shared with us, is just a small step to dive into it. Stay tuned for more exciting topics on Scrum coming soon.

A big thank you to Serhii for sharing his solid knowledge with us!

Interested in startups, unicorns, and Silicon Valley? Explore basic terms and useful English expressions here.

Share this article