Scrum framework - one pager on Scrum

SCUM iconographic visualisation

This is an example of SCRUM iconographic visualisation. Such an iconographic is an excellent tool to sum up and visualize all information which you can post in your blog article, e-book or in a podcast. Sketch notes like that are used by many innovative companies or event organizers.

Scrum is a framework based on the so-called Agile Programming Manifesto and is frequently used in different companies dealing with different projects. Here are the basics of this framework:

Responsibilities

Scrum distinguishes the Product Owner, i.e. the business representative, the Scrum Master, i.e. the person responsible for operating in accordance with Scrum and the associated efficiency, and Developers who simply deal with production work. All of these people together form a Scrum Team that has two characteristics. It is interdisciplinary, i.e. it has all the necessary competences to deliver value, and it is self-managing, i.e. it decides on the best way to do its job.

To understand these roles better see the above Scrum iconographic visualisation

Events

All stakeholders organize work and improve communication during work on the product, each has its own specific goal and imposed maximum duration (the so-called maximum timebox). These are:

Sprint – it lasts a maximum of one calendar month during which the Scrum Team should do something useful and valuable from a business point of view. It includes all the remaining events and productive work of Developers. The new Sprint starts immediately after the end of the previous one.

Sprint Planning – answers 3 questions: why what the team is supposed to do is valuable in our opinion, what is the goal, what we have to deliver in the following Sprint and how we will do it. It lasts a maximum of 8 hours for a monthly Sprint.

Daily Scrum – daily, in the same place and at the same time, maximum 15 minutes planning for the next 24 hours and inspection of the Sprint goals achievement.

Sprint Review – a review and summary of what the team has provided by the past Sprint. Part of it is a demonstration of functionalities on which stakeholders provide feedback. It takes up to 4 hours.
Sprint Retrospective – often referred to as “Retro” for short, the aim of this event is to discuss efficiency, processes, communication, tools and planning specific improvements to be implemented from the next Sprint. The maximum timebox is 3 hours.

You can see all those steps visualized in an excellent way in the scrum iconographic visualisation above.

Scrum Artefacts

All artefacts should be transparent and understandable. Product Owner manages and organizes the artefact called Product Backlog, which is the only source of requirements in Product development (which is not in the backlog – does not exist). As part of the Sprint Planning, the Scrum Team sets its goal and selects which Product Backlog items will be completed in the next Sprint, creating the next Sprint Backlog artefact. All completed according to the so-called “Definition of Completion”, the useful items in the Backlog form the third artefact or Increment.

Scrum values

The use of the above Scrum mechanics will not bring the desired results if the team members do not follow the five values on which the framework is based, which are: Commitment, Focus, Openness, Respect, Courage.

This is also visualised in the scrum iconographic visualisation above.