Scrum Methodology is explained well.

1. Scrum
Agile For Everyone
OMSATS
C Vehari

2. What Is Scrum?
 Scrum (the name is derived from an activity
that occurs during a rugby match

3. By Jeff Sutherland and his development team.
Scrum is a subset of Agile. It is a lightweight process framework for agile
development, and the most widely-used one.
Agile is a time boxed, iterative approach to software delivery that built
software incrementally.
Introduction:
What Is Agile?

4. Some Agile Methodologies are:
Agile
Methodologies
KanBanDSDM
Xp Crystal
Scrum

5. Productivity and efficiency:
87% said their 93% Said adopting
team were Agile helped them
more productive improve speed to
using agile market

6. Scrum has been used by:

7. Commercial
software
Fixed-price
projects
Contract
development
Websites
Video game
development
Embedded
systems

8. To manage complex software's
Increases productivity and reduces
time
Adjust smoothly to rapidly-changing
requirements
Build Quality in
Why to Use Scrum?
Provide better estimates while
spending less time creating them

9. Quicker ROI
Lower Total Cost
Reduce Risk

10. Teaming
Quality Work
Sense Of Done
Visible Progress

11. Cycle Of Scrum

12. Change
No changes during a sprint:

13. Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment

14. Sprint Planning Meeting
Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment
 The first meeting to kick off the sprint.
 Attended by : Scrum Master,
Development Team, the Product Owner
invited stakeholders.
 Product owner describes the highest
priority features to the team.
 At the end team developed the Sprint
Backlog

15. Daily Cycle
Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment
 It is 15 minute meeting held every day.
 In daily Scrum Meeting , Scrum Master
Ask the Three Questions:
 What have you done since the
last meeting?
 Are there any obstacles in the
way of meeting your goal?
 What will you do before the next
meeting?

16. Product Increment
Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment
 The sum of all the product backlog
Items completed during a sprint and
all previous sprints.
 At the end of a sprint, the increment
must be complete.

17. Sprint View
Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment
 It is like the demo of new product.

18. Sprint Retrospective
Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment
 Usually done after sprint and also
after sprint review. The meeting
is facilitated by the Scrum Master
and the product owner.

19. Update Product Backlog
Scrum
Process
Sprint View
Sprint
.Retrospective
Update
. product
backlog
Sprint
Planning
. Meeting
Daily
Cycle
Product
Increment
 After each sprint is given to owner
he may update their requirements.

22. Do not allow changes
Work in the sequence
Validation at sprint Review
Does not prescribe any
engineering practices
Team allow changes
Work in a strict priority order
Validation All time
Prescribe engineering
practices
Scrum Xp.

23. Scrum
Vs.
Waterfall
Iterative
Requirement will change
Unknown Steps
Daily meeting
Not Iterative
Requirement will not
Change
Known Steps
Not Daily Meetings
Scrum
Water
Fall

24. Roles

25. Product
Owner
Team
Scrum
Master

26. Sprint
Planning
Sprint
Review
Daily
Scrum
Meeting

27. Product
Backlog
Sprint
Backlog

28. •Define the features of the
product
•Prioritize features according
to market value
Product Owner
Product Owner
Scrum
Master
Team

29. •Represents management to
the project
•Removes impediments
•Ensure that the team is fully
functional and productive
Scrum Master
Product Owner
Scrum
Master
Team

30. •Define the features of the
product
•Prioritize features according
to market value
Team
Product Owner
Team Scrum
Master

31. •A collaborative meeting in
the beginning of each Sprint.
•Takes 8 hours and consists of
2 parts
Sprint Planning
Sprint Planning
Sprint
Review
Daily
Scrum
Meeting

32. •Is a meeting in which team
members make commitments
to each other and to the
Scrum Master
Daily Scrum Meeting
Sprint Planning
Sprint
Review
Daily
Scrum
Meeting

33. •Is held at the end of each
Sprint
•Team presents what it
accomplished during the
sprint
Sprint Review
Sprint Planning
Sprint
Review
Daily
Scrum
Meeting

34. •Requirements for a system,
expressed as a prioritized list
of Backlog Items
•Usually is created during the
Sprint Planning Meeting
•Is managed and owned by a
Product Owner
Product Backlog
Product
Backlog
Sprint
Backlog

35. •A subset of Product Backlog
Items, which define the work
for a Sprint.
•Estimates are updated
whenever there’s new
information.
•Changes
Sprint Backlog
Product
Backlog
Sprint
Backlog

36. Advantage:
 Agile scrum helps the company in saving time and money.
 Cutting edge developments can be quickly coded and tested
using this method.
 Mistake can be easily corrected.
 It is easier to deliver a quality product in a scheduled time.
Disadvantage:
 Team members leave during a development. (Huge Effect)
 This methodology needs experienced team members only.
 Difficult for the Scrum master to plan, structure and
organize a project that lacks a clear definition.

37. Improvement:
 Allow the team to determine their Sprint capacity.
 Work is not added during the Sprint.
 The team has permission to add work to the Sprint to
make improvements.