What is Scrum and why is important to take it into account when managing projects.

1. Marynarki Polskiej 163, 80-868 Gdańsk, Poland
Scrum

2. What is Scrum?
Scrum – a framework which consists of iterative and incremental attitude towards troubleshooting complex issues.
It allows to deliver a product of the highest possible value in a productive and creative way.

3. What is Scrum?
Within this framework, the process of delivering a product is
separated into smaller iterations called Sprints, which facilitate rapid
and suitable reactions to changes that accompany the development
of this product. Every Sprint may be considered as a new project
whose duration should not exceed one month and which should lead
to achieving the Sprint Goal. The final
effect of every Sprint is always a product
version that is finished and ready to use.

4. Agile Manifesto
Individuals and interactions
Working software
Customer collaboration
Responding to change
Processes and tools
Comprehensive documentation
Contract negotiation
Following a plan
The Scrum framework is frequently used in IT projects, while creating and developing a software. It is based on Agile
Principles and its rules are also true to the Agile Manifesto guidelines. The Agile Manifesto is concise and very simply says
that we can develop software better by valuing the items on the left side of the list more than the items on the right side.

5. The importance of communication
Methodologies that follow Agile values focus mainly on people,
communication, and collaboration. These are the elements that have the
biggest influence over the success of the project – its realization is
impossible when there appear barriers to communication, even when the
most qualified team is provided.

6. Waterfall vs Scrum
Requirements
Analysis
System Design
Implementation
Testing
Deployment
Maintenance
There is a clear difference between the Scrum framework
and the traditional Waterfall model. The Waterfall
development involves several actions which can be
regarded as separate project stages. They are run in turn,
one after another and each has to be finished before
commencing the next stage. This way of working surely
does bring in systematicity but its biggest shortcoming is
the lack of flexibility, which constricts product’s adaptation
to change.
In contrast to the Waterfall model, Scrum framework
considers the whole Sprint as a distinct project stage, not
an action. Everything that is included in a product after
each iteration works.

7. Waterfall vs Scrum
Waterfall Scrum
What happens if you need to stop production for whatever reason?
● Waterfall model → you have to finish what was already started,
● Scrum framework → improving the product may be continued.

8. Components of Scrum
Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage:
Artifacts – they maximize transparency
of key information so that everybody
has the same understanding of it;
Events – they systematize the whole
process;
Roles – they form the Scrum Team;
Rules – they make a close connection
between all the other elements.

9. Artifacts
Product
Backlog
Sprint
Backlog
Product Increment

10. Artifacts
● Product Backlog – an ordered list of everything that is known to be needed in the product (features,
functions, requirements, enhancements, fixes). The Product Backlog is never complete – it is subject to a
continuous process of improvement. The earliest development of it lays out the initially known and
best-understood requirements. The Product Backlog evolves along with the product, the environment in
which it will be used, and the increasing knowledge of the whole team. The Product Backlog is dynamic
– it constantly changes to identify what the product needs to be appropriate, competitive, and useful.
● Sprint Backlog – image of work that Development Team plans to carry out during a Sprint. It consists of:
- a set of Product Backlog items selected for the Sprint,
- a plan for delivering the Product Increment and realizing the Sprint Goal.
● Product Increment – substantial result of all the work that has been done. It represents another step
toward a vision or a goal. At the end of the Sprint a new Product Increment must be in an useable
condition. Product Increment is the sum of:
- all the Product Backlog items completed during a Sprint,
- the value of the increments of all previous Sprints.

11. Events
Sprint
Retrospective
Daily
Scrum
Sprint
Review
Sprint
Planning

12. Events
The heart of Scrum framework is a Sprint, which contains and consists of all the other Events:
● Sprint Planning (max 8h) – it includes determining the Sprint Goal and planning the work to be performed in the
Sprint. Sprint Planning answers the following:
- What can be delivered in the Product Increment resulting from the upcoming Sprint?
- How will the work needed to deliver the Product Increment be achieved?
● Daily Scrum (max 15min) – every day Development Team meeting, which is held at the same time and place and
serves planning the work for the next 24 hours. This optimizes team collaboration and performance by inspecting
the work since the last Daily Scrum and forecasting upcoming Sprint work.
● Sprint Review (max 4h) – it is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog
if needed. During the Sprint Review, attendees collaborate on the next things that could be done. The result of the
Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.
● Sprint Retrospective (max 3h) – it occurs after the Sprint Review and prior to the next Sprint Planning. The Sprint
Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be
enacted during the next Sprint.

13. Roles
Product
Owner
Scrum
Master
Development Team

14. Roles
There exist three basic roles in a Scrum Team:
● Product Owner – a sole person responsible for maximizing the value of the product resulting from work of the
Development Team and managing the Product Backlog. The Product Owner may do the work, or have the
Development Team do it. However, the Product Owner remains accountable.
● Development Team – self-organizing and cross-functional team of 3-9 professionals who do the work of delivering
finished and potentially releasable Product Increment at the end of each Sprint. Individual Development Team members
may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
● Scrum Master – a sole person who is responsible for promoting and supporting team members and the whole
organization by helping everyone understand the Scrum theory, practices, rules, and values.

15. Rules
Transparency Adaptation
Inspection

16. Rules
According to the Scrum framework, the process control is upheld by three pillars:
● Transparency – all of the aspects of the process must be visible and comprehensible to
those who take part in the project, so it is important for them to be defined by a common
standard.
● Inspection – regular verification of Scrum Artifacts and progress toward a Sprint Goal in
order to detect undesirable variances.
● Adaptation – immediate enhancement of those aspects of the process that deviate
outside acceptable limits and can cause that the resulting product will be unacceptable.

17. Scrum Teams
Scrum Teams help to optimize flexibility, creativity and productivity. They are:
● self-organizing – they choose how best to accomplish their work, rather
than being directed by others outside the team;
● cross-functional – they have all competencies needed to accomplish the
work without depending on others who are not a part of the team.

18. Sources
● https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-Polish.pdf
● https://www.scrumguides.org/scrum-guide.html
● https://www.qagile.pl/scrum/scrum-opis/
● https://www.scrum.org/resources/what-is-scrum?gclid=EAIaIQobChMIsIe07Yq43AI
VV-aaCh2VmQwbEAAYASAAEgLQfvD_BwE
● http://www.agile247.pl/scrum/
● https://www.youtube.com/watch?v=Z9QbYZh1YXY
● https://www.youtube.com/watch?v=2Vt7Ik8Ublw
● https://www.youtube.com/watch?v=idDtKI8GM-A
● https://www.youtube.com/watch?v=_U7Py7W-Qng

19. Questions?
Marynarki Polskiej 163, 80-868 Gdańsk, Poland

20. Thank You!
Marynarki Polskiej 163, 80-868 Gdańsk, Poland
Karina Człapińska
Bartosz Wojciechowski
Agata Kurleto