Agile the most famous SDLC technique. This presentation helps you know what is Agile Scrum all about. It also helps you know about, - Sprint Planning - Scrum Meeting - Effort Estimation - Common Mistakes in sprint planning

1. Agile Scrum
By Varun Sukheja

2. SDLC Models
Various types of model
modmodel
● Waterfall model
● V model
● Incremental Model
● RAD model
● Agile Model
● Iterative Model
● Spiral Model

3. What is Agile
Model of
Software
Development ?

4. Agile SDLC model is a
combination of
iterative and
incremental process
models with focus on
process adaptability
and customer
satisfaction by rapid
delivery of working
software product.

5. ● Customer satisfaction by rapid, continuous delivery of useful software.
● People and interactions are emphasized rather than process and tools. Customers,
developers and testers constantly interact with each other.
● Working software is delivered frequently (weeks rather than months).
● Face-to-face conversation is the best form of communication.
● Close, daily cooperation between business people and developers.
● Continuous attention to technical excellence and good design.
● Regular adaptation to changing circumstances.
● Even late changes in requirements are welcomed
Advantages of Agile model

6. What is SCRUM
all about ?

7. SCRUM
Scrum is an Agile
framework for completing
complex projects. Scrum
originally was formalized
for software development
projects, but it works well
for any complex,
innovative scope of work.
The possibilities are
endless. The Scrum
framework is deceptively
simple.

9. Product backlog
The product owner creates a
prioritized list of ideas for the
product, called a product backlog.
The product backlog helps the
team break the product into
smaller, more manageable pieces
and build it incrementally in a
series of short time periods called
sprints. Sprints typically last one
to four weeks.

10. SCRUM
During sprint planning, the team pulls a small chunk of items from the
top of the product backlog to create a sprint backlog, and then decides
how to accomplish those items during the next sprint.

11. The sprint
1. During the sprint, the team meets each day, in a Daily
Scrum, to assess progress and make necessary
adjustments.
2. Along the way, the ScrumMaster keeps the team focused
on its goal. The ScrumMaster also removes impediments
for the team, so everyone can focus and move forward
with their work.
3. At the end of the sprint, the work should be potentially
shippable: ready to hand to a customer, put on a store
shelf, or show to a stakeholder.
4. The sprint ends with a review of the product and a
retrospective of the team's work process, relationships,
and tools.
5. Once a sprint is complete, the team chooses another
chunk of the product backlog, and the next sprint begins.

12. Sprint Planning
PART-1
● Part one of the sprint planning meeting is a
review of the product backlog items the Product
Owner will ask the team to forecast and deliver.
● This is the time for the product owner to
describe what he wants to see built for the next
sprint.
● During this part of the meeting, it is not
uncommon for the team to banter back and
forth with the product owner, asking clarifying
questions and driving away ambiguity.
● By the end of sprint planning part one, the team
will select a sprint goal: a one-sentence
description of the overall outcome of the sprint
● If the work does not directly tie to the sprint
goal, then it is not done during the sprint.

13. Sprint Planning
PART-2
● During part two of the sprint planning meeting,
the team decides how the work will be built.
● In this meeting the team will begin
decomposing the product backlog items into
work tasks and estimating these in hours.
● The product owner must be available during
this meeting but does not have to be in the
room. In fact, many teams find it helpful to
work without product owner during this
detailed part of the meeting.
● If the product owner does remain in the room,
the ScrumMaster needs to take charge of this
part of the meeting, keeping the team focused
and free to explore possibilities without being
limited by the product owner’s own ideas or
opinions.

14. Common mistakes in Sprint Planning

15. How to do Effort
Estimation in
planning ?

16. Effort
Estimation
● The objective of the Estimation
would be to consider the User
Stories for the Sprint by Priority
and by the Ability of the team to
deliver during the Time Box of
the Sprint.
● The size of the Product
Increment is estimated in terms
of User Story Points. Once the
size is determined, the effort is
estimated by means of the past
data, i.e., effort per User Story
Point called Productivity.

17. Effort
Estimation
Different types of scales that are
used in Scrum Estimation
● Numeric Sizing (1 through 10).
● T-shirt Sizes (XS, S, M, L, XL
XXL, XXXL)
● Fibonacci Sequence (1, 2, 3, 5, 8,
13, 21, 34, etc.)
● Dog Breeds (Chihuahua,………,Great
Dane)

18. Planning Poker Technique

19. Queries