Scrum

Scrum Breccan McLeod-Lundy (Certified ScrumMaster)

Roles
Scrum Master
Product Owner
Team member

Product Owner
Decides what features are needed
Prioritizes features
Explains features to the team
There can be only one

Team
Works as a multi-talented group
Commits to tasks
Self-manages

Scrum Master
Acts as a facilitator
Maintains the scrum process
Assists with removing problems for the teams
Is not an interface between the team and product owner

Timeboxing
Time in Scrum works on the basis of timeboxes
Meetings of all types should be strictly time boxed
Releases and sprints are also timeboxed to dates.

Product Backlog
A list of the features that could be included in the product.
In priority order
Can be reordered by the product owner at will.

Release Planning
Initial discussion between the team and product owner trading information.
Lays out goals for the project and identifies when a viable release could occur.
Longest meeting in the entire project. Still wouldn't normally be more than 3 hours.
Includes deciding 'done definition' and initial estimates on tasks.

Done
The done definition defines when a task becomes considered done.
Must include everything that is required for something for something to be done.
Would normally include testing requirements, documentation etc.
Some requirements can be separate tasks instead of being in the done definition.

Initial Estimates
The team gives ballpark estimates on the tasks in the product backlog
Allows the product owner to fix any glaring problems in the cost benefit of how they've prioritized tasks.
A number of techniques are available to assist the estimation process.

Sprint Planning
The team selects tasks from the top of the product backlog to complete in the sprint.
Product owner can clarify details of features or requirements.
Based on an amount that they believe they can take through to done in the given time period.
The team commits to this work as the scope for the current sprint and moves it to the sprint backlog.

Sprint Backlog
Cannot be changed
Tracks the tasks that are part of the sprint
Stages should suit the project. We mostly use:
Not started, in progress, in test, to be verified by client and done
Put somewhere visible so that the teams knows what's happening.

Daily Scrums
Short(1-2 minutes per team member) daily meetings.
Only team members speak
Consists of each team member saying: what they did in the last day, what they'll do in the next day and if anything is blocking them.
Can spawn followups where necessary(blocks, common tasks etc.)

Sprint Review
Team shows off things that are done.
Review status of product backlog with done tasks completed.
Collaborative discussion regarding what could likely come next on the product backlog with the product owner.

Retrospective
Team members and scrum master only.
Team reviews its development process to see what they think went well and what went badly in the last sprint.
Suggests and adopts changes they would like to make to the approach in the next sprint to improve the development process.

Product and Sprint Burndowns
Track the completion of tasks and stories.
Allow for an easy view of velocity in a project. So problems can be caught.
Knowing velocity makes it easier for the team to judge the number of tasks to pick up in future sprints.

Scrum

by breccan on Dec 01, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 34

Statistics

Scrum — Presentation Transcript

http://www.breccan.com	33
http://www.blogger.com	1