Basic Terms (Simple Explanations) Flashcards
(22 cards)
Burndown Charts
Burndown charts show work remaining over time.
Daily Scrum Meeting
A fifteen-minute daily meeting for each team member to report on what they did yesterday, what they plan to do today and impediments hampering their work.
Impediments
Anything that prevents a team member from performing work as efficiently as possible.
Product Backlog
The features of a system, product or service, e.g., a wish list.
Product Backlog Item
A unit of work small enough to be completed by a team in one Sprint iteration. Backlog items are decomposed into one or more tasks.
Product Backlog Item Effort
A rough guess concerning how much effort it will take to complete the work.
Product Burndown Chart
A “big picture” view of a project’s progress. It shows how much work was left to do at the beginning of each sprint.
Product Owner Role
Represents the customer’s interest in prioritizing backlog items.
Release
An increment of potentially shippable product from the Scrum team.
Release Burndown Chart
The release burndown chart is a “big picture” view of a release’s progress.
Scrum Roles
There are three essential roles in any Scrum project: Product Owner, ScrumMaster, Scrum Team
ScrumMaster Role
A facilitator for the team and product owner, rather than managing the team, the ScrumMaster works to assist both the team and product owner.
Sprint
An iteration of work during which an increment of product functionality is implemented, e.g., two weeks.
Sprint Backlog
Defines the work for a sprint, represented by the set of tasks that must be completed to realize the sprint’s goals, and selected set of product backlog items.
Sprint Burndown Chart
A visual measurement tool that shows the completed work per day
Sprint Goals
Sprint goals are the result of a negotiation between the product owner and the development team. Scrum focuses on goals that result in demonstrable product.
Sprint Planning Meeting
The Sprint planning meeting is a negotiation between the team and the product owner about what the team will do during the next sprint.
Sprint Retrospective Meeting
The sprint retrospective meeting is held at the end of every sprint after the sprint review meeting. The team and ScrumMaster meet to discuss what went well and what to improve in the next sprint.
Sprint Task
A unit of work generally less than 12 hours. Team members volunteer for tasks.
Team
A team (or “Scrum team”) is optimally comprised of 7, plus or minus 2 people. It is cross-functional and self-organizes.
Team Member
Anyone working on sprint tasks toward the sprint goal.
Velocity
How much product backlog effort a team can handle in one sprint.