Metrics
Measurement of a team's ability to deliver work in a sprint
Capacity
1 to 4 week project period
Sprint
Anyone internal or external to an organization who has an interest in the project
Stakeholder
An iterative, collaborative approach to work, prioritizing customer needs and embracing change
Agile
Year Agile Manifesto created
2000
A team's estimation of the effort required to complete a user story or task
Story Points
A showcase of what the team achieved during the sprint
Sprint Review
Responsible for maintaining Agile process & practice on their team
Scrum Master
Ongoing process of reviewing, clarifying and prioritizing user stories
Refinement
Conditions a user story must meet to be considered complete and ready for review
Acceptance Criteria
Average amount of work a scrum team completes during a sprint, very useful for forecasting
Velocity
Quick, 15-minute meeting to align on tasks
Daily Standup
Creates and prioritizes the backlog
Product Owner
Value individuals and interaction over ...
Strict Processes and Tools
A prioritized list of work items, features or tasks that need to be completed
Backlog
Used to manage scope creep
Epic and release burndown
Frequent feedback loops that allow for continuous improvement
Retrospective
Person within an organization who helps identify the customer need and business objectives for a new product or feature
Product Manager
Document that outlines the values and principles of Agile
Manifesto
Visualization of work on a board with columns representing different stages of the workflow
Kanban
Period between the moment of making a request for delivering a product and the actual delivery
Lead Time
Review and prioritization of tasks in queue
Grooming
Responsible for the planning, procurement and execution of a project
Project Manager
Framework emphasizing limited work in progress to optimize flow and efficiency
Scrum
Short, simple description of a feature, written from the end user perspective
User Stories