Scrum methodology introduction. Why informal human way works? Read the blog: http://blog.infodiagram.com/2015/11/presenting-scrum-process-creative-slides.html Step by step presentation of Scrum process, who is involved, what roles people play - from stakeholder, product owner, scrum master to product developers. Listing the Scrum meetings types such as weekly sprint meetings, daily stand ups, retrospectives and backlog grooming. Scrum is great project management methodology especially for complex projects with high uncertainty level.

2. Scrum is an Agile framework
for completing complex projects.
Definition:

3. Scrum is an Agile framework
for completing complex projects.
Originally formalized for software development
projects, but it works well for any complex,
innovative scope of work.
Definition:

4. Scrum is an Agile framework
for completing complex projects.
Originally formalized for software development
projects, but it works well for any complex,
innovative scope of work.
The Scrum framework is deceptively simple.
Definition:
Source: http://www.scrumalliance.org/why-scrum

5. History
OOPSLA
(conference)
1995

6. History
OOPSLA
(conference)
Agile Manifesto
2001
1995

7. History
OOPSLA
(conference)
Agile Manifesto
Agile Software
Development with
Scrum (book)
2001
1995 2001

8. History
OOPSLA
(conference)
Agile Manifesto
Founding of the
Scrum Alliance
Agile Software
Development with
Scrum (book)
2001
1995 2001
2002

9. History
OOPSLA
(conference)
Agile Manifesto
Founding of the
Scrum Alliance
Agile Software
Development with
Scrum (book)
First Scrum
Master
education
2001
1995 2001
2002
2003

10. Scrum methodology
…has success
in the software
development

11. Scrum methodology
…has success
in the software
development
… works
with a few rules

12. Scrum methodology
…has success
in the software
development
… works
with a few rules
… works in nearly
every domain

13. Scrum methodology
…has success
in the software
development
… works
with a few rules
…focus on
teams rather
than individuals
… works in nearly
every domain

14. Scrum process

15. Scrum process
Vision
Product
Backlog

16. Scrum process
Potentially
shippable
Product
Product
Backlog
Vision

17. Scrum process
Potentially
shippable
Product
Iterative
product
development
Vision
Product
Backlog

18. Scrum process
Daily
Stand-Up
Sprint
Potentially
shippable
Product
Product
Backlog

19. Who’s involved?

20. Who’s involved?
Stakeholder

21. Who’s involved?
Stakeholder
Product Owner

22. Who’s involved?
Stakeholder
Product Owner
Scrum
Master

23. Who’s involved?
Developers
Stakeholder
Product Owner
Scrum
Master

24. Who’s involved?
Developers
Stakeholder
Product Owner
Sprint Review
Daily Stand-Up
Scrum
Master
Sprint

25. Who’s involved?
Scrum – the agile project management framework
Provides transparency to the project status at any time

26. Scrum Roles
STAKEHOLDERSSCRUM TEAM

27. Scrum Roles
STAKEHOLDERS
Scrum Master Product Owner
(Development)
Team
SCRUM TEAM

28. This is a part of presentation
resources we create
with our contributors.

29. This is a part of presentation
resources we create
with our contributors.
Check more presentation visuals.
Visit us, help us create new ones
at infoDiagram.com
(click to open)

30. This is a part of presentation
resources we create
with our contributors.
See more examples…
Check more presentation visuals.
Visit us, help us create new ones
at infoDiagram.com
(click to open)

31. 5 types of Scrum Meetings

32. 5 types of Scrum Meetings
Sprint
Planning

33. 5 types of Scrum Meetings
Daily
Scrum
Sprint
Planning

34. 5 types of Scrum Meetings
Daily
Scrum
Sprint
Review
Sprint
Planning

35. 5 types of Scrum Meetings
Daily
Scrum
Sprint
Review
Retrospective
Sprint
Planning

36. 5 types of Scrum Meetings
Daily
Scrum
Sprint
Review
Retrospective
Backlog
Grooming
Sprint
Planning

37. When to use Scrum?
Stacy Landscape Diagram

38. When to use Scrum?
Stacy Landscape Diagram
Unknown
Technology
Known
Technology

39. When to use Scrum?
Stable
requirements
Unstable
requirements
Stacy Landscape Diagram
Unknown
Technology
Known
Technology

40. When to use Scrum?
Stable
requirements
Unstable
requirements
Stacy Landscape Diagram
Unknown
Technology
Known
Technology

41. When to use Scrum?
Stable
requirements
Unstable
requirements
Stacy Landscape Diagram
Unknown
Technology
Known
Technology

42. Scrum Methodology Techniques

43. Information Radiator
A place in the team room where
everybody can access it
Put important information on it,
so everybody can see this

44. User Story
A promise for discussion
No classic requirement
artifact
Documents requirements
from the user point of view
As a <role>,
I want <goal/desire>
so that <benefit>

45. Story Points
I need
4 hours
I need
12
hours
I need
8 hours
The complexity of a
story is always the
same
As a <role>,
I want <goal/desire>
so that <benefit>
An abstract way to measure
the complexity of a user story.

46. Planning Poker
3
Define a reference story,
Assign a value
Everybody gets a set
of Planning poker cards
Discuss a story
Pull up the cards
at the same time

47. Niko Niko Calendars
Collect the mood of each team
member

48. Niko Niko Calendars
Collect the mood of each team
member
Feel the team‘s mood and
get chance to react. 1 2 3 4 5 6 7

49. Niko Niko Calendars
Collect the mood of each team
member
Feel the team‘s mood and
get chance to react. 1 2 3 4 5 6 7

50. Niko Niko Calendars
Collect the mood of each team
member
Feel the team‘s mood and
get chance to react. 1 2 3 4 5 6 7
Ups, a bad day

51. Niko Niko Calendars
Collect the mood of each team
member
Feel the team‘s mood and
get chance to react. 1 2 3 4 5 6 7

52. Explaining Scrum can be easy & fun.
Just use less formal way of presenting it.

53. Explaining Scrum can be easy & fun.
Just use less formal way of presenting it.

54. Explaining Scrum can be easy & fun.
Just use less formal way of presenting it.
Download these slides
at infoDiagram.com
(click to open)

55. For more presentations,
hit FOLLOW on slideshare.net/infodiagramFollow
Download these slides
at infoDiagram.com
(click to open)