Agile Cheat Sheet
ADVERTISEMENT
1AGILE CHEAT SHEET *
Roles
Artifacts
Meetings
Scrum Team
Product Backlog - (PB)
Sprint Planning - Day 1 / First Half
Estimating
User Stories
Scrum teams are self organizing.
Maintained by the Product Owner.
Product backlog prepared prior to meeting.
Team is cross-functional and consists of 5-9
List can contain bugs, and non-functional items.
First half - Team selects items committing to complete.
High level definition of user requirements
people.
Product Owner responsible for prioritizing.
Additional discussion of PB occurs during actual
that serves as a starting point for discussion.
There are no set project roles within the team.
Items can be added by anyone at anytime.
Sprint.
Building blocks that can be assigned priorities,
Team defines tasks and assignments.
Each item should have a business value assigned.
Sprint Planning - Day 1 / Second Half
estimates, completion status.
Usually Dev : QA ratio is 3:1. Team develops the
List of all desired product features.
Large user stories (Epics) that take longer than a
product as per sprint backlog.
Product backlog can be organized as a prioritized list
Occurs after half done - PO available for questions.
sprint to build are broken into smaller user stories.
Ensures team works on highest valued features.
of user stories in order of “high-risk, high-value”, “low-
Team solely responsible for deciding how to build.
User stories are NOT dependent on other stories.
risk, high-value”, “low-risk, low-value”.
Tasks created / assigned - Sprint Backlog produced.
Story Template: As a <User>, I want <function>
Product Owner - (PO)
So that <desired result>
Daily Scrum
Sprint Backlog - (SB)
Story Example: As a user, I want to print a recipe
Accountable for product success.
Held every day during a Sprint.
so that I can cook it.
Defines all product features.
To-do list (also known as Backlog item) for the Sprint.
Lasts 15 minutes.
Story Points
Responsible for prioritizing product features.
Created by the Scrum Team.
Team members report to each other not to Scrum
Maintains the Product Backlog.
Product Owner has defined as highest priority.
Master.
Story points indicate relative degree of difficulty
Ensures team works on highest valued features.
Answers 3 questions during meeting.
Burndown Chart - (BC)
and they follow the Fibonacci series because it
One full time product owner for every scrum team.
“What have you done since last daily scrum?”
represents a set of numbers that we can intuitively
“What will you do before the next daily scrum?”
Chart showing how much work remaining in a Sprint.
distinguish between them as different magnitudes.
“What obstacles are impeding your work?”
Scrum Master - (SM)
Calculated in hours remaining.
Example: ”Send to a Friend” Story Points = 2
Opportunity for team members to synchronize their
Maintained by the Scrum Master daily.
“Shopping Cart” Story Points = 8
Holds daily 15 minutes team meeting.(Daily Scrum)
work.
Maintain seperate account of work remaining out of the
“Advanced Search” Story Points = 13
Removes road blocks.
Having daily scrum over a conference call in
“Original RB” and “New Features” added during the
Business Value
Facilitates planning and estimation.
distributed teams is not advisable.
release.
Maintains the Sprint Burndown Chart.
Distributed teams are advised to break in multiple
Each User Story in the Product Backlog should have
Release Backlog - (RB)
Conducts Sprint Retrospective at the end of every
colocated teams.
a corresponding business value assigned.
Sprint.
Typically assign (L, M, H) Low, Medium, High.
Sprint Review
Maintains team spirit.
Same as the Product Backlog. May involve one or
PO prioritizes Backlog items by the highest value.
Typically one scrum master can handle two scrum
more sprints dependent on determined Release date.
User Stories can be classified as “Must have”,
teams.
Team presents “done” code to PO and stakeholders.
“Should have”, “Could Have”, “Good to have”.
“DONE”= Potentially Shippable!
Functionality not “done” is not shown.
TDD = Refactoring + TFD
Feedback generated - RB may be reprioritized.
Planning Poker
FAQ
Scrum Master sets next Sprint Review.
Testing via xUnit Framework
Cards bearing Fibonacci numbers
Refactor code
3a
[tests unbroken]
are distributed to all team members. Stories are
Sprint Retrospective
Who decides when a Release happens? At the end
discussed and team members place cards, face
of any given Sprint the PO can initiate a Release.
Refactor code
Refactor code
3b
down, containing their estimation for each story.
Attendees - SM, PO and Team.
[Test(s) broken]
[tests broken]
Who is responsible for managing the teams? The
All Tests
One or more
Cards are opened and the highest and the lowest
Questions - What went well and what can be
teams are responsible for managing themselves.
Pass
Tests fail
bidder debate to support their estimate.
improved?
What is the length of a task? Tasks should take no
Fix Functional code
2
SM helps team in discovery - does not provide
It is repeated till team converges on the estimate.
4
longer than 16 hours. If longer, then the task should be
Can’t think
answers.
broken down further.
Velocity
of any
Write a test
1
Who manages obstacles? Primary responsibility is
more
Visibility + Flexibility = Scrum
tests
The rate (Story Points per Sprint) at which team
on the Scrum Master. However, teams must learn to
converts items to “DONE”.
resolve their own issues. If not able, then escalate to
Kanban
After a few iterations velocity, becomes stable
SM.
XP Practices
and predictable.
What are two of the biggest challenges in Scrum?
Applies to any process that has sequence of steps.
Teams not self-managing, Scrum Master managing,
WIP-Limit - maximum WIP allowed at any step is
Testing and Automation
XP - Extreme Programming.
not facilitating.
fixed. WIP-Limit can be quantified in Story Points.
TDD - Test Driven Development, Routine Refactoring.
How to add new User Stories to SB in the middle of
Typical steps - Requirement clarification,
Manual QA and Dev are co-located, and in 1:3 ratio,
BDD - Behaviour Driven Development.
sprint? It is not advisable. Sprint should be short
development, integration, testing, deployment, UAT.
for new products. Automation QA team is separate.
TFD - Test First Development.
enough to allow new user stories to wait till the next
Add or move resources to wherever the bottleneck is
Continuous testing using automation for early defect
CI - Continuous Integration.
sprint starts. In exceptional cases, a new user story
observed. Of course, the bottleneck may keep
detection.
CD - Continuous Deployment.
can be added by removing one or more stories to
moving.
Automation lags by a sprint to allow recent test
UAT - User Acceptance Testing.
keep the total of story points constant.
Works well for ongoing support/maintenance work.
cases to stabilize.
SYNERZIP
* Inspired by ScrumLogic
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Education