Scribd
Upload
151 views20 pages

CSM - Online - 01 - Agile Foundations

Scrum is an agile framework that focuses on iterative development and continuous improvement. It includes events like sprint planning, daily standups, sprint reviews and retrospectives. The main artifacts are the product backlog, sprint backlog and increment. Scrum values working software over documentation and values individuals and interactions over processes. It aims to deliver value to customers through short development cycles and collaboration between self-organizing cross-functional teams.

Uploaded by

ABHISHEK BHALOTIA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
151 views20 pages

CSM - Online - 01 - Agile Foundations

Scrum is an agile framework that focuses on iterative development and continuous improvement. It includes events like sprint planning, daily standups, sprint reviews and retrospectives. The main artifacts are the product backlog, sprint backlog and increment. Scrum values working software over documentation and values individuals and interactions over processes. It aims to deliver value to customers through short development cycles and collaboration between self-organizing cross-functional teams.

Uploaded by

ABHISHEK BHALOTIA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Certified Scrum Master

Agile / Scrum Foundations


Certification Levels
Scrum Introduction
• Scrum is not a methodology that will make you develop better products;
• Scrum does not provide the answers to how to build quality software
faster;
• Scrum is a tool, a framework, you can use to find out what you need to do
to build quality software faster.
• Scrum does not require team collocation;
• However, with Scrum, you can measure the productivity of collocation.

Ken Schwaber
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping
others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left
more.
The 12 principals of Agile Manifesto
Agile vs Traditional Development
Waterfall Agile

The Plan creates cost/ The Vision creates feature


schedule estimates estimates

Fix These Features Cost Schedule

VALUE/VISION
DRIVEN
PLAN
DRIVEN

Estimate These Cost Schedule Features


The Scrum Framework
The 3 Scrum Artefacts
• The Product Backlog
• The Sprint Backlog
• The Increment
The Product Backlog
• The Product Backlog is an ordered list of everything that is known to
be needed in the product.
• A Product Backlog is never complete
• The earliest development of it lays out the initially known and best-
understood requirements
• The Product Backlog evolves as the product and the environment in which it
will be used evolves
• The Product Backlog is dynamic; it constantly changes to identify what the
product needs to be appropriate, competitive, and useful
The Sprint Backlog
• The Sprint Backlog is the set of Product Backlog items selected for the
Sprint, plus a plan for delivering the product Increment and realizing
the Sprint Goal
• The Sprint Backlog makes visible all the work that the Development
Team identifies as necessary to meet the Sprint Goal
• The Sprint Backlog is a plan with enough detail that changes in
progress can be understood in the Daily Scrum
The Increment
• The Increment is the sum of all the Product Backlog items completed
during a Sprint and the value of the increments of all previous Sprints
• At the end of a Sprint, the new Increment must be "Done," which
means it must be in useable condition and meet the Scrum Team’s
definition of "Done“
• The increment is a step toward a vision or goal
The 5 Scrum Events
• Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
Sprint
• A fixed time of one month or less during which a "Done", useable,
and potentially releasable product Increment is created
• Sprints have consistent durations throughout a development effort
• A new Sprint starts immediately after the conclusion of the previous
Sprint
• Sprints contain and consist of the Sprint Planning, Daily Scrums, the
development work, the Sprint Review, and the Sprint Retrospective
• No changes are made that would endanger the Sprint Goal
Sprint Planning
• The work to be performed in the Sprint is planned at the Sprint
Planning
• This plan is created by the collaborative work of the entire Scrum Team
• Sprint Planning is time-boxed to a maximum of eight hours for a one-
month Sprint
• For shorter Sprints, the event is usually shorter
• Sprint Planning answers the following:
• What can be delivered in the Increment resulting from the upcoming Sprint?
• How will the work needed to deliver the Increment be achieved?
Daily Scrum
• The Daily Scrum is a 15-minute event for the Developers
• The Daily Scrum is held every day of the Sprint
• This optimizes team collaboration and performance
• The structure of the meeting is set by the Development Team
• Some Developers will use questions, some will be more discussion
based
• The Daily Scrum is an internal meeting for the Developers
Sprint Review
• During the Sprint Review, the Scrum Team and stakeholders
collaborate about what was done in the Sprint
• Based on that attendees collaborate on the next things that could be done to
optimize value
• This is an informal meeting, not a status meeting
• This is at most a four-hour meeting for one-month Sprints
• For shorter Sprints, the event is usually shorter
• The result of the Sprint Review is a revised Product Backlog that
defines the probable Product Backlog items for the next Sprint
Sprint Retrospective
• The Sprint Retrospective is an opportunity for the Scrum Team to
inspect itself and create a plan for improvements
• This is at most a three-hour meeting for one-month Sprints
• For shorter Sprints, the event is usually shorter.
• The purpose of the Sprint Retrospective is to:
• Inspect how the last Sprint went with regards to people, relationships,
process, and tools
• Identify and order the major items that went well and potential
improvements
• Create a plan for implementing improvements to the way the Scrum Team
does its work
Scrum Values
• When the values of commitment, courage, focus, openness and
respect are embodied and lived by the Scrum Team, the Scrum pillars
of transparency, inspection, and adaptation come to life and build
trust for everyone. The Scrum Team members learn and explore
those values as they work with the Scrum events, roles and artifacts.

You might also like