What's the story
Every user story should have an actor, a feature or function, and this.
Purpose or expected outcome
Agile suggests that team are this.
Self-organizing
The most important rule is that this MUST happen every day.
Stand up
Represented by the set of stories or features that must be completed prior to an initial launch
Minimum Viable Product (MVP)
??
???
How do engineers know what will be included in a User Acceptance Test (UAT) before the story can be closed.
Acceptance criteria
In Scrum, what team role(s) may act as Scrum Master (with training)?
Any role!
Who runs stand up
Anybody. It is a meeting by the team for the team.
Who decides on final prioritization of stories in the backlog
Product Owner
Do this when a story is too big to be delivered within the team norms
Story splitting
Fibonacci sequence is often used to do what
Assign Story Points
Name two non-engineering roles on an Agile delivery team
Product Owner and Agile Delivery Lead (or Scrum Master)
The ceremony does not appear formally in Agile best practices
Grooming (or Refinement)
This method of prioritization helps teams to identify the next items to work on.
Stack rank
Ignoring this important practice in Agile will lead to additional tech debt
Code refactoring
Who assigns story points?
Teams thrive when they make this a priority
Continuous improvement
This ceremony only applies to Scrum Agile teams
Sprint Planning
The best indicator of the value of the features delivered is
User feedback
We value working software over...
[action] the [result] [by|for|of|to] a(n) [object] is an example of what alternative to the traditional User Story format
Feature-Driven Development (FDD)
This person developed the model of 5 Stages of Team Development; forming, storming, norming, performing, and adjourning
A retrospective looks at the the immediate past to help identify process improvements for the team. This looks back at a project to call out needs to maximize the chance of success for future projects
Lessons learned or Post Mortem
In 2015 the Standish Group estimates that this percentage of feature are used often (within 5%)
32% (41% infrequently used, 27% hardly ever used)
This document kicked off the Agile movement
The Agile Manifesto