Sept 2009 Edition

Objective

 Learn the basics of Scrum

 Learn the roles in Scrum

 Learn the Scrum Artifacts

Outline

 What is Scrum?
 The Scrum Process Flow
 Values
 Roles
 Scrum Events
 Artifacts
 Terminology
What is Scrum?

 An iterative incremental framework for managing complex work; Scrum

framework consists of scrum team and their roles, events, artifact, and rules.

 Lightweight process for managing and controlling software and product

development in rapidly changing environments.

 Commonly used in agile software development;

Scrum Components
Values

 Commitment – personally commit to achieving the goals of the scrum

team.

 Courage – do the right thing and work on tough problems.

 Focus – Everyone focuses on the sprint goal.

 Openness – Open communication

 Respect – Scrum team respects each other to be capable, independent

people.
Roles in Scrum

 Product Owner

 Scrum Master

 Development Team

 Stakeholders
Roles(the who)

Product Owner

 Represents the voice of the customer / Represents the stakeholders

 Ensures that the Scrum Team works with the "right things" from a
business perspective.
 Writes user stories.
 Prioritizes them and then places them in the product backlog.
Roles(the who)

Scrum Master

 Facilitates Scrum
Primary job is to remove impediments to the ability of the
team to deliver the sprint goal.
Not the leader of the team (as the team is self -organizing)
but acts as a buffer between the team and any distracting
influences.
Ensures that the Scrum process is used as intended.
Enforcer of rules.
Protects the team and keep them focused on the tasks in
hand.
Roles(the who)

Development Team

Has the responsibility to deliver the product.

 Typically made up of 5–9 people with cross-

functional skills who do the actual work (design,
develop, test, technical communication, etc.).
Roles (the who)

Stakeholders (Customers, Vendors, etc)

 People who enable the project

 For whom the project will produce the agreed-upon benefit[s]
which justify its production.
 They are only directly involved in the process during the sprint
reviews.
Scrum Events

 The Sprint

 Sprint Planning

 Daily Scrum

 Sprint Review Meeting

 Sprint Retrospective
Scrum Events

The Sprint

 A time – boxed of 2 weeks up to 1 month during which

a “done”, useable and potentially shippable product
increment is created.
 It has consistent durations during the development
effort.
 Sprints consist of sprint planning, daily scrums,
development work, review and sprint retrospective.
Scrum Events

Sprint Planning Meeting

 A collaborative meeting at the beginning of each Sprint between

the Product Owner, the Scrum Master and the Team
 Time-boxed maximum of 8 hours.
 Identify and communicate how much of the work is likely to be
done during the current sprint
Scrum Events

Sprint Planning Meeting

 1st Part:
 Choosing user stories from the Product Backlog
 Determining the Sprint Goal.
 Participants: Product Owner, Scrum Master, Scrum Team
 2nd Part:
 Participants: Scrum Master, Scrum Team
 Creating Sprint Backlog
Scrum Components
 Scrum Events

Daily Scrum

 Each day during the sprint, a project status meeting occurs. This is called
a "daily scrum", or "the daily standup". This meeting has specific
guidelines: The meeting starts precisely on time.

 All are welcome, but only the Scrum Team may speak
 The meeting is timeboxed to 15 minutes
 The meeting should happen at the same location and same time every
day
 During the meeting, each team member answers three questions:
- What have you done since yesterday?
- What are you planning to do today?
- Do you have any problems preventing you from
accomplishing your goal?
Scrum Components
Scrum Events

Sprint Review Meeting

 Held at the end of the sprint.

 The scrum team and stakeholders review what was
done in the sprint.
 This is an informal meeting, not a status meeting
and the presentation of the features is intended to
elicit feedback and foster collaboration.
 Four hour time limit
Scrum Components
 Scrum Events

Sprint Retrospective

 All team members reflect on the past sprint.

 Make continuous process improvement.
 It occurs after sprint review.
 The questions:
- What should we as a Team start doing?
- What should we as a Team stop doing?
- What should we as a Team keep doing?
- Did we achieve the Sprint Goal?
Scrum Components
Artifacts

 Product Backlog

 Sprint Backlog

 Burn Down Chart

Artifacts …

Product Backlog

 List of requirements for a system

 Expressed as a prioritized list of Backlog Items
 Is managed and owned by a Product Owner or/and through the
Scrum Master
 Can be changed and re-prioritized before each PM
Artifacts …

Estimation of Product Backlog

 Establishes team’s velocity

(how much Effort a Team can handle in one Sprint)
 Determining units of complexity via Story Points
 Methods of estimation:
 Expert Review
 Planning Poker
Artifacts …

Sprint Backlog

 A subset of Product Backlog Items, which define the work for a

Sprint
 Sprint Backlog Tasks are created ONLY by Team members
 Each Item has its own status
 Should be updated everyday
Artifacts …

Burn Down Charts

 Are used to represent “work done.”

 Are wonderful information radiators
 3 Types:
 Sprint Burn down Chart (progress of the Sprint)
 Release Burn down Chart (progress of release)
 Product Burn down chart (progress of the Product)
Artifacts …

Sprint Burn Down Chart

 Depicts the total Sprint Backlog hours remaining per day

 Shows the estimated amount of time to release
 Ideally should burn down to zero to the end of the Sprint
 Actually is not a straight line
 Can bump UP
Artifacts …

Release Burn Down Chart

 Will the release be done on right time?
 X-axis: sprints
 Y-axis: amount of hours
remaining
 The estimated work remaining
can also burn up
Artifacts …

Product Burn Down Chart

 Is a “big picture” view of project’s progress
(all the releases)
Definition of Done

 Scrum team must have a shared understanding of

what it means for work to be complete to ensure
transparency.

 Done is defined at the start of the Project.

Terminologies

 Impediment

 Sprint

 Velocity
Terminologies

 Impediment - Anything that prevents a team member from

performing work as efficiently as possible.

 Sprint - A time period (typically 1–4 weeks) in which development

occurs on a set of backlog items that the Team has committed to.

 Velocity - It is a measure of the amount of work done by a Team

during a single Sprint.
Thank You!