The document provides an overview of Scrum, an agile software development process. It discusses the history and principles of Scrum, describes Scrum roles, processes, artifacts, and how Scrum enables rapid delivery of working software in short iterations through self-organizing cross-functional teams and empirical process control. The advantages of Scrum include delivering working software frequently and improving productivity, while disadvantages include potential ineffectiveness for small projects and high implementation costs.

1. Presented By,
Praveen Reddy
P . Lakshmi
V . Priyanka
Kishore

2. ◦ Introduction To Scrum
◦ History of Scrum
◦ Principles of Scrum
◦ Characteristics Of Scrum
◦ Functionality Of Scrum
◦ Components of Scrum
 Scrum Roles
 The Process
 Scrum Artifacts
◦ Advantages Of Scrum
◦ Disadvantages Of Scrum
◦ Conclusion

3.  Scrum is an Agile Software Development
Process
 SCRUM is a lightweight process for
managing and controlling software and
product development in rapidly changing
environments.
 Scrum is an agile process that allows us to
focus on delivering the highest business
value in the shortest time.

4. 1995 : Scrum by Jeff Sutherland & Ken Schwaber.
1996 : introduction of Scrum at OOPSLA
conference
 2001 :publication “Agile Software Development
with Scrum” by Ken Schwaber & Mike Beedle
Successful appliance of Scrum in over 50
companies
Founders are members in the Agile Alliance

5.  Quality work: empowers everyone involved to be
feel good about their job.
 Assume Simplicity: Scrum is a way to detect and
cause removal of anything that gets in the way of
development.
 Embracing Change: Team based approach to
development where requirements are rapidly
changing.
 Incremental changes: Scrum makes this possible
using sprints where a team is able to deliver a
product (iteration) deliverable within 30 days.

6.  Self-organizing teams
 Product progresses in a series of month-long
“sprints”
 Requirements are captured as items in a list of
“product backlog”
 No specific engineering practices prescribed
 Uses generative rules to create an agile
environment for delivering projects
 One of the “agile processes”

9.  Scrum Roles
 The Process
 Scrum Artifacts

10.  Scrum Master
 Developer
 QA
 Documentation member
 Project manager

11.  Represents management to the project
 Typically filled by a Project Manager or
Team Leader
 Responsible for enacting scrum values
and practices
 Main job is to remove impediments

12.  Typically 5-10
people
 Cross-functional
(QA, Programmers,
UI Designers, etc.)
 Members should be
full-time
 Team is self-
organizing

13.  Sprint Planning Meeting
 Sprint
 Daily Scrum
 Sprint Review Meeting

14.  A collaborative meeting in the
beginning of each Sprint between the
Product Owner, the Scrum Master and
the Team
 Takes 8 hours and consists of 2 parts
(“before lunch and after lunch”)

15.  A month-long iteration, during which is
incremented a product functionality
 NO outside influence can interference with
the Scrum team during the Sprint
 Each Sprint begins with the Daily Scrum
Meeting

16.  Is a short (15 minutes
long) meeting, which is
held every day before the
Team starts working
 Participants: Scrum
Master (which is the
chairman), Scrum Team
 Every Team member
should answer on 3
questions

17.  Is held at the end of each
Sprint
 Business functionality
which was created during
the Sprint is
demonstrated to the
Product Owner
 Informal, should not
distract Team members
of doing their work

18.  Product Backlog
 Sprint Backlog
 Burn down Charts

19.  Requirements for a system, expressed as a prioritized list
of Backlog Items
 Is managed and owned by a Product Owner
 Spreadsheet (typically)
 Usually is created during the Sprint Planning Meeting
 Can be changed and re-prioritized before each PM

20.  A subset of Product Backlog Items, which
define the work for a Sprint
 Is created ONLY by Team members
 Each Item has it’s own status
 Should be updated every day

21.  Are used to represent “work done”.
 Are wonderful Information Radiators
 3 Types:
◦ Sprint Burn down Chart (progress of the
Sprint)
◦ Release Burn down Chart (progress of
release)
◦ Product Burn down chart (progress of the
Product)

23.  Completely developed and tested features
in short iterations
 Simplicity of the process
 Clearly defined rules
 Increasing productivity
 Self-organizing
 each team member carries a lot of
responsibility
 Improved communication
 Combination with Extreme Programming

24.  Scrum is not effective for small
projects
 Expensive to implement
 Training is required

25.  Scrum offers:
◦ a high degree of flexibility
◦ promises a high probability of success
 Scrum benefits:
◦ an anticipating culture
◦ increases the sense of urgency
◦ promotes the sharing of knowledge
◦ encourages dense communications
◦ facilitates honesty among developers