Scrum Reference Card

Scrum Reference Card by Michael James

About Scrum

Scrum Roles

A Management Framework

Product Owner

Scrum is a management framework for incremental product development using one or more cross-functional, self-organizing teams of about seven people each.

¥ Single person responsible for maximizing the return on investment
(ROI) of the development effort

It provides a structure of roles, meetings, rules, and artifacts. Teams are responsible for creating and adapting their processes within this framework. Scrum uses fixed-length iterations, called Sprints, which are typically two weeks or 30 days long. Scrum teams 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-value features first, incorporating feedback sooner.
Requirements
Analysis

¥ Responsible for product vision
¥ Constantly re-prioritizes the Product Backlog, adjusting any longterm expectations such as release plans
¥ Final arbiter of requirements questions
¥ Accepts or rejects each product increment
¥ Decides whether to ship
¥ Decides whether to continue development
¥ Considers stakeholder interests
¥ May contribute as a team member
¥ Has a leadership role

Scrum Development Team
¥ Cross-functional (e.g., includes members with testing skills, and often others not traditionally called developers: business analysts, domain experts, etc.)

Design
Code

¥ Self-organizing / self-managing, without externally assigned roles
¥ Negotiates commitments with the Product Owner, one Sprint at a time Integration
Test
Deploy

Figure 1: Traditional “waterfall” development depends on a perfect understanding of the product requirements at the outset and minimal errors executing each phase.

¥ Has autonomy regarding how to reach commitments
¥