Scrum Framework

2. What is Scrum?
Scrum is one of the flavor of Agile or is a framework for managing software delivery
that comes under the broader umbrella of agile project management. It provides a
lightweight process framework that embraces iterative and incremental practices,
helping organizations deliver working software more frequently. Scrum has certain
guidelines which help in becoming any team Agile. Here people can address complex
adaptive problems, while productively & creatively delivering products of the highes
possible value.

3. Scrum Framework

4. Sprints…
 In Scrum the iterations that deliver working software to the customers are called Sprints.
 Goal - In each iteration for Sprints results potentially shippable software
 Overhead costs - Every Sprint should have Sprint Planning meeting, Sprint Review & Sprint
Retrospective
 Agile project favors shorter duration sprint

5. 5
Backlog
• Product Backlog
The agile product backlog in Scrum is a prioritized features list, containing short descriptions of all functionality desired in the product.
product backlog item ("PBI", "backlog item", or "item") is a unit of work small enough to be completed by a team in one Sprint
iteration. Backlog itemsare decomposed into one or more tasks
• Release Backlog
A release backlog is a subset of the product backlog that is planned to be delivered in the coming release, typically a three- to six-month
horizon. It would presumably contain the same type of items as on a product backlog
• Sprint Backlog
Basically, a Sprint Backlog is a list of tasks identified by the Scrum team and these tasks have to be completed during the Scrum sprint.
Here, the team selects some product backlog items mainly in the user stories form

6. 6
Scrum Ceremonies
• Sprint Planning Meeting
Sprint planning is a collaborative effort involving a ScrumMaster, who facilitates the meeting, a Product Owner, who clarifies the details of
the product backlog items and their respective acceptance criteria, and the Entire Agile Team, who define the work and effort necessary to
meet their sprint commitment
• Daily Scrum
In Scrum, on each day of a sprint, the team holds a daily scrum meeting called the "daily scrum.” ... Ideally, a daily scrum meeting is held in
the morning, as it helps set the context for the coming day's work. These scrum meetings are strictly time-boxed to 15 minutes. This keeps
the discussion brisk but relevant.
• Sprint Review
In Scrum, each sprint is required to deliver a potentially shippable product increment. This means that at the end of each sprint, the team
has produced a coded, tested and usable piece of software. ... During this meeting, the Scrum team shows what they accomplished during
the sprint.
• Sprint Retrospective
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. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.

7. Scrum Roles
Product Owner:
Manage the ROI
• Establishes baseline ROI
• Measure project against this baseline
• Priotizes Product Backlog to maximize ROI
Guide Product Development
• Owns & communicates product vision
• Defines & prioritizes feature according to market values
• Adjust features & priorities every sprint, as needed
Call for Release
• Decides on release data & content of Product
• Can shift a release forward & backward to maximize ROI based on new knowledge

8. Scrum Roles
Scrum Master:
• Removes barrier from the team
• Shields Team from external interferences
• Improve productivity
• Enforce Scrum principles
• Enable close cooperation

9. Scrum Roles
Scrum Team:
• Continous collaboration
• Focus on steady delivery
• Team composition doesn’t change
• Cross functional skill set
• Self organizes

10. Thank you