jira Flashcards
An epic is
a large user story
A user story is a
feature
User stories are formatted like
As a (role), I want (feature), so that (benefit)
The list of features is called
product backlog
The scrum masters job is
make sure the project is progressing, the team members have the tools they need, he sets up meetings, monitors the work being done, and schedules release planning
The user stories that are chosen to be built go into the
release backlog
the user stories in the release backlog get
prioritized by the team, and then the amount of time for each story is estimated. Large user stories are sometimes split up into smaller ones
You can estimate the total amount of work that needs to get done by
summing all the estimates for all the user stories in the release backlog.
The best way to estimate the amount of work for each product is to
estimate hours. Note: some people use story points, where they compare the difficulty to small component with a known level of difficulty.
The estimate times usually get put into
1h, 2h, 4h, 8h
2d, 3d, 5d, 10d
1m, 2m, 3m, 6m
a sprint is
a milestone between 2 and 30 days, where you do a set of user stories that will be ship ready together. The goal is to get a subset of the release backlog into a ship-ready state.
At the end of each sprint you should have
a fully tested product with all the features of the sprint 100% tested.
a release backlog gets broken down into a
multiple sprint backlogs
A burndown chart is
a graph of all the remaining work over every day in either a sprint or release.
The slope of the turndown chart can help you predict
How long the sprint or release will take. AKA burndown velocity.