DZone, Inc.
|
www.dzone.com
By Michael James
ABOUT SCRUM
Scrum www.dzone.com Get More Refcardz! Visit refcardz.com
#50
Scrum
Scrum is a simple management framework for incremental
product development using one or more cross-functional, self-
organizing teams of about seven people each.
Scrum teams use fixed length iterations, called Sprints, typically
two weeks or 30 days long. They attempt to build a potentially
shippable (properly tested) product increment every iteration.
An Alternative to Waterfall
Scrum’s incremental, iterative approach trades the traditional
phases of “waterfall” development for the ability to develop a
subset of high-business value features first, incorporating user
feedback sooner.
Figure 1: Traditional “waterfall” development assumes perfect understanding of
requirements at outset.
Project
Start
Iteration 1
QA / Acceptance
Testing
Design &
Analysis
Implementation & Developer Testing
Evaluation /
Prioritization
Detailed
Requirements
(Deployment)
Iteration
Detail
Iteration 2 Iteration 3 Iteration 4
Project
End
Figure 2: Scrum blends all development activities into every iteration, adapting to
discovered realities at fixed intervals.
Scrum has been used for a variety of products, but has initially
been most popular for software products using object-oriented
technologies. It is particularly suited to high risk endeavors
where traditional efficiency concerns are secondary to the
ability to deliver the right product, or any product, by the
required date.
A Disruptive Framework to Transform Organizations
The reality checks forced by the short feedback loops are
intended to expose dysfunction at the individual, team, and
organizational level. Rather than modify Scrum to mask these
dysfunctions, organizations are encouraged to challenge these
SCRUM ROLES
Product Owner
The Product Owner is the single individual responsible for
return on investment (ROI) of the product development
effort. The Product Owner owns the product vision, constantly
re-prioritizes the Product Backlog, and revises release plan
expectations. The Product Owner is the final arbiter of
requirements questions, including which items are considered
“done” at the Sprint Review Meeting.
Scrum Development Team
The Team is a self-organizing/-managing group of about seven
(give or take two) individuals. While the Team may contain
specialists, collectively it is cross-functional, containing the
range of skills (including testing) which were traditionally
found in different departments. The Team is given autonomy
regarding how to achieve the commitments they’re held
responsible for between the Sprint Planning and Sprint Review
meetings.
A Scrum Development Team is most likely to succeed when
members are co-located in a team room.
Requirements
Analysis
Design
Code
Integration
Test
Deploy
constraints and transform themselves.
Scrum is a framework, not a defined process or methodology.
Scrum provides a simple structure of roles, meetings, rules,
and artifacts
1
. Scrum teams are responsible for creating and
adapting their processes within this framework. Scrum’s
management practices are similar to those of eXtreme
Programming (XP), but, unlike XP, Scrum does not prescribe
specific engineering practices.
Danube Technologies, Inc.
www.danube.com
+1.503.248.0800
CONTENTS INCLUDE:
n
About Scrum
n
Scrum Roles
n
Scrum Meetings
n
Scrum Artifacts
n
Scaling
n
Related Practices and more...