Scrum is an agile framework for managing projects developed by Jeff Sutherland in 1993 based on earlier work. It uses short "sprints" to iteratively develop work items prioritized in a backlog. Key roles include the Product Owner who prioritizes the backlog, the Scrum Master who facilitates the process, and the cross-functional Scrum Team. Each sprint involves planning, daily stand-ups, development, review, and retrospective. The process is intended to be flexible and transparent compared to traditional sequential models like waterfall.

1. SCRUM
PROCESSING
MODEL
BY :
Noime Amado
Wenafrida A. Ordejan
Bsit-3C

2. Who develops Scrum processing
model ?
Dr. Jeff Sutherland created the Scrum process in 1993, taking the term
“Scrum” from an analogy in a 1986 study by Takeuchi and Nonaka
and Nonaka published in the Harvard Business Review.
Sourced by: www.smartsheet.com

3. SCRUM
• is an Agile Process for running
Software Development Project.
• uses an Empirical Process control model.
Sourced by: www.smartsheet.com

4. www.contolchaos.com

5. Steps in the Scrum
Process
 Product backlog: The Product Owner and Scrum Team meet
to prioritize the items on the product backlog (the work on
the product backlog comes from user stories and
requirements).
 Sprint planning: Before each sprint, the Product Owner
presents the top items on the backlog to the team in a
sprint planning meeting.
Sourced by: www.smartsheet.com

6. Sourced by: www.smartsheet.com
 Backlog refinement/grooming:The team may remove
user stories that aren’t relevant, create new
stories, reassess the priority of stories, or split user stories
into smaller tasks.
 Daily Scrum meetings: The Daily Scrum is a 15-minute
stand-up meeting where each team member talks about
their goals and any issues that have come up.

7. The Daily Scrum Meeting
 Within the Sprint, the Scrum Team gathers in the same place at the same time
each work day.
 Provides daily chance to “Inspect and Adapt.”
 The Scrum Master asks each person, in turn:
- “What have you done since the last Scrum meeting?”
- “What do you plan to do before the next Scrum meeting?”
- “What impediments are in your way?”
After the Daily Scrum, the teams gets to work and the Scrum Master sets about
removing impediments.

8. Sourced by: www.smartsheet.com
 Sprint review meeting: This meeting should feature
a live demonstration, not a report or a PowerPoint
presentation.
 Sprint retrospective meeting: The team may talk
about what went well during the sprint, what went
wrong, and what they could do differently.

9. Roles in Scrum
Product Owner- The Scrum Product Owner has
the vision of what he or she wants to build and
conveys that vision to the team. The Product
Owner focuses on business and market
requirements, prioritizing all the work that needs
to be done.
Scrum Master: Often considered the coach for
the team, the Scrum Master helps the team do
their best possible work.
Scrum Team: The Scrum Team is comprised of five
to seven members. Everyone on the project works
together, helps each other, and shares a deep
sense of camaraderie.
Sourced by: www.smartsheet.com

10. Product Backlog
 Prioritized list of all features and changes that have yet to
be made to the system.
 High-level and loosely defined - estimated from 1 – 20 days
or so.
 The Scrum Master is the owner of the Product Backlog.
Before beginning the first Sprint, the Product Manager and
the Scrum Team produce an initial Product Backlog.
www.slideshare.net

11. Advantages of Scrum processing
model
 More transparency and project visibility
 Increased team accountability
 Easy to accommodate changes
 Increased cost savings
Sourced by: www.smartsheet.com

12. Disadvantages of Scrum processing
model
 Risk of scope creep
 Team requires experience and commitment
 The wrong Scrum Master can ruin everything
 Poorly defined tasks can lead to inaccuracies
Sourced by: www.smartsheet.com

13. Difference of Scrum toother
Agile model
Sourced by: www.smartsheet.com
Scrum, on the other hand, is a subset of Agile. A Scrum is a simple and
flexible Agile methodology for software development.
The Scrum is not a technique or a process but a lightweight and simple
framework to address complex problems of a project and deliver a high-value
product creatively .
While waterfall methodology is a sequential design process. This means that
as each of the eight stages (conception, initiation, analysis, design, construction,
testing, implementation, and maintenance) are completed, the developers move on
to the next step.