SCRUM – how it looks like in practice

The main advantage of the SCRUM framework is that it is uncomplicated and easy to implement. In fact it requires a bit of practice, experience and first of all a change of the way of thinking about making the product, but it brings measurable benefits for the Client and all the project participants. SCRUM consists of the following elements:

Pillars

  • Transparency ensures that all aspects related to work are visible, accessible and equally understood by all parties involved.
  • Review ensures that Scrum artefacts (Product Backlog, Sprint Backlog, Increment) and progress are regularly reviewed to detect any deviations from expectations.
  • Adaptation ensures that when the inspection process detects discrepancy from expected results, appropriate adjustments are made.

Roles

  • The Product Owner is responsible for making decisions about product development and the use of the Development Team’s time, to build as much value as possible. He understands well the business needs related to the developed product, and knows what the stakeholders’ expectations are set on the shape of the final product and what the goals are. The product owner receives and accepts the work done by the Development Team.
  • Development Team is responsible for planning, organizing, and executing the work. It is a self-organizing team with competences necessary to produce a product and achieve the goals indicated by the Product Owner.
  • SCRUM Master is responsible for putting SCRUM rules into practice, understanding and following the rules of the framework. He supports the team through the facilitation and removal of obstacles.

Artefacts

  • Product Backlog – a list of things to be done based on which the Development Team plans and executes the work. The product backlog should always be up to date to show how many things need to be done.
  • Sprint Backlog – a list of things to do in a given Sprint. Sprint Backlog should always be up to date to show the progress of the work. The sprint backlog is created during the planning based on the collaboration between the product owner and the development team. The sprint backlog consists of user stories, which then serve as a basis for the tasks for the development team.
  • Increment – the completed, tested, and integrated increment of functionality and product features that show what is done and how it looks.

Events

  • Sprint planning meeting, where the SCRUM Team collectively defines what will be done in the upcoming Sprint.
  • Daily SCRUM – daily meeting (up to 15min.), where the Team “synchronizes”. Team members talk about what they did, and what they are going to do, and if they see any obstacles
  • Sprint review – the Team presents what they have completed in the sprint. The Clinet takes part in the meeting and presentation. The Team is open to questions, criticism, remarks and appreciation.
  • Sprint retrospective the least formal meeting. The goal is to improve the process.

All the elements indicated above make up the SCRUM cycle indicated in this diagram:

Share on linkedin
Share on facebook
Share on twitter

You may also find interesting:

Product Design Sprint

Design Sprint is a process of business problems solving developed by Google Ventures. It was created to help start-ups build better products. We adapted this method to the requirements of big organizations.

Design-Driven Innovation

Innovation is often about changing the meaning of what a product or a service is and what it offers its users. This is the core of the design.

UX & Visual Design

Interfaces, processes, and ecosystems, improve customer journeys, help to increase sales, and provide better customer service. We combine business and users’ needs to create digital products that make money.

Scrum at a glance

SCRUM has become the dominant approach to organising project work. The high variability of the economic and legal environment forces companies to increase the speed of adaptation.

Contact us