Scrum Roles
Scrum Meetings
Scrum Artifacts
Scrum User Stories
Scrum Values
100
Works based on shared commitment, proactively looks for help if needed, is ideally co-located so planned collaboration is not needed, collaborates to complete take highest priority stories all the way to done.
Who is the team?
100
Meeting to understand each team members commitments and any road blocks preventing progress (Not a status meeting).
What is the daily scrum?
100
Requirements expressed as user stories, in a force ranked prioritized list.
What is the Product Backlog?
100
As a [user role] I want [ability] so that [benefit]
What is the user story syntax (format)?
100
To make a pledge or promise; Take responsibility for something.
What is Commitment?
200
Servant leader with no management authority, sits with the team, brings burndown chart to each daily scrum, and helps to remove impediments so the team stays focused on the sprint goal.
Who is the Scrum Master?
200
Meeting to demonstrate working software and gain feedback from stakeholders.
What is the sprint review?
200
The set of tasks that must be completed to realize the sprint's goals.
What is the Sprint Backlog?
200
A type of story used for activities such as research, design, exploration and even prototyping.
What is a Spike Story?
200
To have a central point, as of attraction, attention, or activity, concentrate on the work at hand.
What is Focus?
300
Single person who represents the stakeholders, is the voice of the customer, provides direction to the team, makes priority decisions, and is responsible for the project success and ensuring that the team delivers value to the business
Who is the Product Owner?
300
Meeting to gather information about the process and choose 1-3 actionable goals that can be immediately addressed in the next sprint.
What is the sprint retro?
300
Depicts the total task hours remaining and shows a quick visual on whether you are on track to deliver by the end of the sprint.
What is the Burndown chart?
300
A story that is too big to fit into a single sprint and must be broken into smaller pieces.
What is an Epic (or large story)?
300
To share information, be truthful, not closed, and demonstrate transparency.
What is Openness?
400
The people for whom the project produces value and benefit[s] Only directly involved in the process during the sprint reviews.
Who are the Stakeholders?
400
Meeting to understand the product owners next highest priority needs, and to estimate how much effort it will take in order to commit to the next sprint.
What is sprint planning?
400
A unit of work generally between 4 and 16 hours.
What is a Task?
400
Answers the question, “How do we know when the story is done?”
What is Acceptance Criteria?
400
To show regard for others rights, beliefs, and points of view.
What is Respect?
500
Tells team members what to do; "command and control" leader
Who is "No one on a scrum team"?
500
Meeting to understand just enough information about work that is likely coming up in the next 1-3 sprints (10% of the current sprints capacity should be used for this).
What is backlog grooming?
500
Specific and measurable, negotiated between the product owner and the team, and reflect the "shippable" code that is expected at the end of the sprint.
What is the Sprint Goal?
500
[I]ndependent [N]egotiable [V]aluable [E]stimable [S]mall [T]estable
What are the charecteristics of a good user story?
500
To have the quality of mind to face difficulty, not being afraid to share the bad news with the good, and avoid burying information.
What is Courage?
M
e
n
u