Show:
Agile Team
Agile Values
Product Backlog
Sprint Planning
Sprint Execution
100
Responsible for maximizing the business value delivered by the team
Who is the Product Owner
100
The document that defines the 4 agile values
What is the Agile Manifesto
100
This is a brief, simple wish or desire from the perspective of the user
What is a user story
100
This meeting starts the current sprint and has the team commit to a group of stories
What is the sprint planning meeting
100
This recurring meeting involves the team and should answer three basic questions
What is the daily standup
200
Responsible for facilitating the Scrum process and ensuring the team is delivering value
Who is the Scrum Master
200
Individuals and interactions over
What are processes and tools
200
A list of items or work in priority order
What is a product backlog
200
This set of work is the backlog committed to for the sprint
What is the sprint backlog
200
Being either virtual or physical, this communicates the progress and status of work
What is the story, task, or Kanban board
300
Responsible for delivering value
Who is the Scrum team
300
Working software over
What is comprehensive documentation
300
Pass all these and the user story might be done
What are acceptance criteria
300
This activity creates all the necessary work to complete a story
What is the task breakdown
300
This chart tracks points left in a sprint
What is a burndown chart
400
Responsible for helping the Product Owner align the team deliverables with the overall company needs
Who are the stakeholders
400
Customer collaboration over
What is contract negotiation
400
A product backlog item aimed at answering a question or gathering information, rather than producing shippable product
What is a spike
400
Who defines what "done" means
Who is the team
400
This chart tracks team capacity
What is the velocity
500
The four stages of team maturity
What is Forming, Storming, Norming, Performing
500
Responding to change over
What is following a plan
500
This acronym mnemonic should be followed when writing user stories
What is INVEST
500
The sprint planning meeting timebox, in hours, if the team runs 3-week sprints
What is 6 hours
500
The number of points a team receives for a partially completed story at the end of the sprint
What is 0