AGILE

PROCESS
A Developers Perspective on
Scrum

SCRUM
a method for project management that is becoming increasingly more
common in the software industry.
Small teams consisting of a maximum 6-8 people divide their work into
mini projects that have a duration of about one month during which a
limited number of detailed tasks are solved. Where traditional methods
focus on staying on track, Scrum is aimed at like other agile methods delivering business value.

Quick look

Who?
What?
How?
Version One/JIRA

Feel free to interrupt !

Who?

Scrum Master (Facilitator)

Person responsible to have the process followed.

Scrum Team
People who create and execute the process flow.

Product Owner
the person responsible for the products
Product Backlog and that the project is working with the right
things from a business perspective.

What?
Roadmap a sequenced, themed plan of intent
Epics Big ideas of features or capabilities
User-stories unit of customer value, completed in a sprint. A

high-level description of an individual feature in the backlog

Tasks granular level of work required to be completed in a

backlog item / defect.

Release(milestone) is a series of Iterations(group of

features).

What?
Burn-down chart a diagram that monitors how much

work remains to implement a segment of the software being

developed during a Sprint.

Daily Scrum - daily meetings (about 15 min) between

the Scrum Master and the Scrum Team. The purpose is to keep
work flowing smoothly and eliminate any impediments.
Sprint Planning - selecting, discussion and estimation of

features for current sprint.

Sprint - the iteration comprised (normally) of thirty days during

which the Scrum Team concentrates on realizing the goals

defined by the projects current Sprint Backlog.

What?
Sprint Retrospective - meeting (about 3 hours) held after

each Sprint. The Scrum Master and the Scrum Team review
both what went well and what should be improved in the next
Sprint.
Sprint Reviews - an informal meeting (about 4 hours) at
the end of a Sprint during which the team presents (and
demonstrates, if relevant) for management, customers and the
Product Owner what has been created during the Sprint.
Timebox - a period during which something is to be carried
out. A Sprint is a result of timebox thinking. Deadlines may not
be exceeded parts of the assignment are deleted instead.

What?

Product Backlog - current to-do list that

contains the
projects goals and priorities. Managed by the
Product Owner.
Epics
User-stories(backlog item)

Sprint Backlog a to-do list for a Sprint.

Consists of the
assignments that the Product Owner has defined
as having the
highest priority. Is given its final structure during
the Sprints first day at a meeting between the
Product Owner and the Scrum Team.
Release Backlog - the same as a Product
Backlog, but restricted to a release of the product.

What are
User
Stories?

User-stories
New features.
Enhancements.
Low-level technical teams.
Architectural / infrastructural items.
Non-functional items such as documentations.
Defects/bugs.
Spikes

How?

1. Sprint Planning
a.Product Backlog (Feature Estimation)
b.Sprint Backlog (Task Estimation)

2. Daily stand-up (scrum meetings)

.

Task re-estimations

Elimination of impediments

Burning of hours

1. Completed, Accepted or Done.

.

Lead review

QA review

Product review

1. Sprint Review.
.

demo

1. Team Retrospective.
.

What went wrong

Project Approach Before

Reference: CollabNet, Scrum Reference

Guide

Project Approach Now

Reference: CollabNet, Scrum Reference

Guide

Project Approach Now, contd

Reference: CollabNet, Scrum Reference

Guide

Product (Development) Backlog

Reference: CollabNet, Scrum Reference

Guide

Version One / JIRA