scrum

agile project management framework that helps teams

structure and manage their work through a set of values,
principles, and practices.
Much like a rugby team
designed to help self-organized teams execute projects
quickly in an agile environment.
 Scrum Values?
Courage, Focus, Commitment,
Respect, and Openness
 Scrum Roles?
The entire Scrum team usually has the following responsibilities:
Breaking down the requirements, creating tasks, estimating,
and distributing them.
Arranging Daily Scrum meetings.
Ensuring that potentially shippable functionality will be
delivered at the end of the Sprint.
Updating statuses and the remaining efforts for their tasks to
allow the creation of a Sprint Burndown diagram.
 Scrum team
Product Owner
define user stories and create a product backlog.
primary point of contact on behalf of the customer to
identify the product requirements for the development
team.
The Product Owner has the complete responsibility and
ownership of defining and even prioritizing user
requirements.
The Product Owner must communicate with the development
team to explain the product features to be implemented.
Any queries that come from the development team must be
addressed by the Product Owner on key user requirements.
The Product Owner has to collaborate and work closely with
various stakeholders such as customers, business leaders,
development teams, project managers, and other
stakeholders.
The product backlog must be clearly defined, and all the items
need to be mentioned elaborately.
Prioritize and order the product backlog in the right manner so
that the important tasks are given topmost priority.
Prioritize work items and product backlog, this must be in line
with customer vision and goals.
Evaluate the work done by the development team and provide
constant feedback.
The Product Owner must ensure that the product backlog is
communicated clearly to all team members.
The Scrum Team must have clarity on the product
requirements and user expectations.
 Scrum Master?

Responsible for ensuring that the Scrum team follows the

processes that were agreed upon.
Keeping obstacles and distractions out of the team's path is
one of the responsibilities of the Scrum master.
Keep all Parties on Track and Informed: hosts daily team
meetings to get updates on the progress of the project,
address potential roadblocks, and ensure that the project is on
track.
Coach Team Members : ensure that the team is
adequately trained to understand Agile processes, the
team members know their specific roles and are
dedicated to the project
Host Daily Stand-up Meetings
Remove Roadblocks
 Development Team
people working together to develop and deliver the
requested and committed product increments.
Scrum developers are cross-functional members
who are capable to achieve the Sprint goals.
The team may include software engineers,
architects, system admins, analysts, UI designers, QA
experts, etc.
 sprints?

A sprint is a short, time-boxed period when a

scrum team works to complete a set amount
of work.
"Sprints make projects more manageable,
allow teams to ship high-quality work faster
and more frequently, and gives them more
flexibility to adapt to change."
 SPRINT
!Sprint planning : What work can get done in
this sprint and how will the chosen work get
done?
Choosing the right work items for a sprint is a
collaborative effort between the product
owner, scrum master, and development team.
DAILY STANDUPS : about how the work is
progressing.
The goal of this meeting is to surface any
blockers and challenges that would impact the
teams ability to deliver the sprint goal.
SPRINT REVIEW : team demonstrates what
they’ve completed
SPRINT RETROSPECT : team reflects on the past
to improve the future.
 Scrum - Artifacts
key
Scrum Team
information that the and the
stakeholders need to be aware of for understanding
the product under development, the activities done,
and the activities being planned in the project.
Product Backlog
Sprint Backlog
Burn-Down Chart
Increment
 Product Backlog
The Product Backlog lists all features, functions,
requirements, enhancements, and fixes that
constitute the changes to be made to the product in
future releases.
Product Backlog items have the attributes of a
description, order, estimate, and value.
These items are normally termed as User Stories.
The Product Owner is responsible for the Product
Backlog, including its content, availability, and
ordering.
 Sprint Backlog

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 is a plan with enough detail that
can be understood by the Team to track in the Daily
Scrum.
The Team modifies the Sprint Backlog throughout the
Sprint,
 Increment

The Increment is the sum of all the Product Backlog

items completed during a Sprint combined with the
increments of all previous Sprints.
At the end of a Sprint, the new Increment must be a
working product, which means it must be in a useable
condition.
 Sprint Burn-Down Chart
At any point in time in a Sprint, the total work
remaining in the Sprint Backlog can be summed.
The Team tracks this total work remaining for
every Daily Scrum to project the likelihood of
achieving the Sprint Goal.
By tracking the remaining work throughout the
Sprint, the Team can manage its progress.
 velocity is the average number of points DONE over the lAST
FEW Sprints.
Capacity Planning?
collect details about the availability of each member of the
Agile team.
You should also know when they will not be available.
After gathering this information, you will have to add up the
number of individuals to evaluate the overall team capacity.
 When to Do Capacity Planning
Before the Sprint Planning.
your team can get better visibility of the availability and
vacation plan of your resources.
How to Perform Capacity Planning
1. Evaluate the Probable Capacity Needs:
2. Judge the Present Capacity and Infrastructure Facilities.
3. Spot Alternatives to Requirements :For instance, you find that
the present capacity is not sufficient to complete the priority
tasks. So, you know that to address the shortage, you will have
to expand the team. To boost capacity, you might need
overtime and additional shift as well.

 User Story?
As a [role], I want [capability], so I [benefit]

Epic?
An epic is a story that is larger than 8 story points
An epic is a story that can’t be completed in one sprint
When you first start planning an agile development project, all
of your user stories will likely be in epic form. Then, as the
Product Owner starts prioritizing, the most important of those
epics will be broken down, down, down into much smaller user
stories.
The Product Owner then prioritizes those stories and the
scrum is a framework that teams and organizations can use
to manage products of different types. Scrum doesn't
dictate which software engineering practices developers
should use
 Extreme programming
Really cares about programming.
Puts a lot of emphasis on the programming
techniques developers should use to ensure
a high-quality result.
But from its very roots, XP has always been a
more technical approach than scrum.
1. Scrum teams typically work in iterations (called sprints) that
are from two weeks to one month long. XP teams typically
work in iterations that are one or two weeks long.
2. Scrum teams do not allow changes into their sprints, XP teams
are much more amenable to change within their iterations.
3. Extreme Programming teams work in a strict priority order.
Features to be developed are prioritized by the customer the
team is required to work on them in that order. By contrast,
the Scrum product owner prioritizes the product backlog but
the team determines the sequence in which they will develop
the backlog items.
 scrum steps
Step 1: Create a scrum project
Step 2: Create user stories or tasks in the backlog
USER STORIES?
describe work items in a non-technical language and from a user's
perspective. . As a {type of user}, I want {goal} so that I {receive
benefit}.
User stories are usually sketched out and prioritized by the
product owner, and then the development team determines
detailed tasks necessary to complete the story in an upcoming
sprint. The development team is also responsible for estimating
the relative effort required to complete the work of the story.
 Step 3: Create a sprint
Create your first sprint in the backlog so you can start
planning the sprint.
Step 4: Hold the sprint planning meeting
In this meeting, the entire team discusses the sprint goal and the
stories in the prioritized product backlog.
The development team creates detailed tasks and estimates for the
high-priority stories.
The development team then commits to completing a certain number
of stories in the sprint.
These stories and the plan for completing them become what is
known as the sprint backlog.
 SPRINT PLANNING MEETING?
Attendees: Required: development team, scrum master, product owner

When: At the beginning of a sprint.

Purpose: Plan the work of the sprint. The team agrees to the sprint goal
and the sprint backlog.
SPRINT GOAL?
When creating a sprint, the product owner usually identifies a sprint
oal. This provides a theme for the work to be completed in the sprint. A
print goal also provides some flexibility in the number of stories that are
ompleted in a sprint. A sprint is considered a success if the sprint goal is
achieved.
 Step 5: Start the sprint

Step 6: Hold the daily standup meetings

Attendees (Primarily): development team

When: Once per day, typically in the morning

Duration: No more than 15 minutes

Purpose: The daily standup is designed to inform everyone
quickly of what's going on across the team and to plan the work
of the day. It's not a full status meeting.

 Step 7: View the Burndown Chart

Burndown Chart shows the actual and estimated amount of work
to be done in a sprint.
Step 9: Hold the sprint review meeting
where the team shows what they've shipped in that sprint. Each
sprint usually produces a working part of the product called an
increment.
Attendees (Primarily): development team, scrum master, product
owner.
 Step 10: Hold the sprint retrospective meeting
After you complete the sprint,
Purpose: The team inspects itself, including its processes, tools
and team interaction. Improvement issues are often added to
the next sprint's backlog.

DONE
Jira Software is an agile project management tool that supports any
agile methodology. From agile boards, backlogs, roadmaps, reports,
to integrations and add-ons you can plan, track, and manage all
your agile software development projects from a single tool.
Team members can easily see what tasks have been assigned to
them.
Jira can also generate reports for discussion during the
retrospective meeting analyzing how the work went.
The high levels of transparency enable better collaboration and
communication across the team. Since the sprint board displays
the tasks assigned to every team member, teams can see who
has bandwidth and who is overloaded during a particular sprint.

 Extreme Programming (XP)

XP is the most specific of the agile frameworks regarding
appropriate engineering practices for software
development.
Values
communication, simplicity, feedback, courage, and
respect
Rather than planning, analyzing, and designing in a
linear fashion, XP programmers do all such activities a
little at a time throughout the development phase.
 Phases of xp
1. Planning :
set goals of the entire project and certain iterative
cycles.
At this stage the team meets with the customer and asks
him on all aspects of the future software.
The customer formulates his vision of the product is user
stories.
The developers estimate and prioritize them in the
release plan.

2. Designing
At this stage of the project the team must define the main
features of the future code.
3. Coding
4. Testing
usually conducted not after the final or intermediate product is
done, but along with the procedure of code writing.
5. Listening
At the final stage of the life cycle the XP team must get a
feedback from the customer.
 XP versus Scrum
1. Iteration length
Scrum
Typically from two weeks to one month long.
XP
Typically one or two weeks long.

Whether requirements are allowed to be modified in an iteration

Scrum
Do not allow changes into their sprints.
Once the sprint planning meeting is completed and a commitment
made to deliver a set of product backlog items, that set of items
remains unchanged through the end of the sprint.
XP
Much more amenable to change.
As long as the team hasn’t started work on a particular feature, a
new feature of equivalent size can be swapped into the XP team’s
iteration in exchange for the un-started feature.

Whether User Story is implemented strictly according to priority

XP
Work in a strict priority order.
Features to be developed are prioritized by the customer
(Scrum’s Product Owner) and the team is required to work on
them in that order.
Scrum
Scrum product owner prioritizes the product backlog but the
team determines the sequence in which they will develop the
backlog items.

 Scrum
Doesn’t prescribe any engineering practices

XP

XP does.
For example: TDD, pair programming, simple design,
refactoring…