Scrum is an agile framework that helps teams deliver customer value early and often through short iterative cycles called sprints. Key roles include the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and the cross-functional team. Ceremonies like the Daily Scrum, Sprint Review and Retrospective support transparency and continuous improvement. The goal is working software delivered incrementally to gain early customer feedback.

1. Agile - Scrum

2. Objectives
• What is Scrum?
• Scrum Vs Waterfall
• 3 Scrum Roles
• 4+1 Scrum Ceremonies
• What is a Sprint?
• 3 Scrum Artifacts
• The Agile Manifesto
• Summary

3. What is Scrum?
Scrum is an iterative and incremental agile software
development framework for managing software projects
and product or application development.
“Scrum” is agile
framework that
helps team deliver
customer value
very early and
often in a highly
predictable
manner.
Published 1995 – Jeff Sutherland
Scrum is not a methodology, it is a framework.

4. Scrum Vs Waterfall
„Scrum‟ takes its cue from RUGBY SCRUM where Waterfall method is the relay race
a team is aggressively trying to advance the ball approach where every individual is
and working together as one unit. doing their part and then passing the
baton to the next person.
Scrum says we need to have a cross functional team and they
have to be focussed on advancing the common goal.

5. Scrum Roles
Product Owner responsible for the business value of the project.
One Person, Responsible for Product backlog and priority, accept/reject work, Knowledgeable, empowered,
engaged, motivator, ROI.
Scrum Master ensures that the team is functional and productive
Organize teams, remove impediments, facilitate healthy process, Empower the Team
The Team self-organizes to get the work done.
Cross Functional, 5 to 9, Committed, Generalising Specialists, deliver value in small chunks within every sprint,
focused on customer, build in quality

6. The chicken & The
Pig
A Pig is someone who has skin in the game. Mike Cohn aptly refers to the people in that role
as, “Having their Bacon on the line.” Pig roles are considered core team members. Performers.
People who “do” work. (Product Owner and Scrum Master)
A Chicken is someone who has something to gain by the Pigs performing, but in the end,
really do not contribute day to day to “getting things done.” Their “eggs” are a renewable
resource, and many get laid.

7. Release Planning after an initial feature list has been identified, prioritized,
and potentially estimated, the team plans an overall release schedule and
determine which features can likely be delivered. Used to feed individual sprint plans.
Sprint Planning the team meets with the product owner to choose a set of
work to deliver during a sprint. (Each task/work estimated @ 1- 16 hours)
Daily Scrum the team meets each day to share struggles and progress.
Sprint Reviews the team demonstrates to the product owner what it has
completed during the sprint. Done features are presented to PO. ( PO, Team, SM, Client.-optional. 1- 3
hours)
Sprint Retrospectives the team looks for ways to improve the product and
the process by identifying the +ve & -ve impacts during the sprint. ( SM, Team. 1
– 4 hours)
Whole team gathers & discusses what they’d like to: Start Doing, Stop Doing, Continue Doing .

8. A sprint is the basic unit of development in Story Point Used to estimate the size of a story.
Scrum. The sprint is a "time boxed" effort, Estimate the height of the dogs as following:
i.e. it is restricted to a specific duration. The 1. Choose the smallest
Use it as 1 story point
duration is fixed in advance for each sprint 2.
3. Estimate all others relatively to the first chosen one
and is normally between one week and
four weeks. •
•
Labrador
Dachshund
• Great Dane
• Australian Terrier
Each sprint is preceded by a planning • German Shepherd
meeting, where the tasks for the sprint are •
•
Poodle
Saint Bernard
identified and an estimated commitment • Doberman
for the sprint goal is made, and followed • Chow Chow
Mastiff
by a review or retrospective meeting,
•
• Japanese Akita
where the progress is reviewed and lessons
for the next sprint are identified.

9. http://www.youtube.com/watch?v=q_R9wQY4G5I
Techniques/Tools – Scrum Board

10. Product Backlog ordered list of ideas for the product. Prioritized
by value delivered to the customer.
Reprioritized at the start of each sprint
Sprint Backlog set of work from the product backlog that the team
agrees to complete in a sprint, broken into tasks.
Individuals sign up for work of their own choosing. Work is never assigned
Burn down/up Chart shows the cumulative work remaining in a
Sprint, day-by-day.
Techniques/Tools - Fibonacci Series, Pareto Analysis, Party Poker

11. a statement of
values
Individuals & Interactions over Process & tools
Working software over Comprehensive
documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan
Source: www.agilemanifesto.org

12. • Scrum is an agile process that allows us to focus on delivering the highest
business value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software in
Sprints.
• The business sets the priorities. Teams self-organize to determine the best
way to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and
decide to release it as is or continue to enhance it for another sprint.
Portions of the presentation sourced from Scrum Alliance, Agile Manifesto and Mountain Goat Software