click to reveal definition
click to flip back
You know 0 of 28 cards in current set.
Ready to get certified?
Get CertifiedNeed this expertise applied inside your organization?
Explore Our ServicesFull Glossary
Agile Foundations
- Agile
- An iterative, incremental approach to delivering value that responds to change through frequent feedback, collaboration, and working solutions.
- Agile Manifesto
- A 2001 statement of four values and twelve principles prioritizing individuals and interactions, working software, customer collaboration, and responding to change.
- Four Values
- Individuals and interactions over processes and tools; working software over documentation; customer collaboration over contract negotiation; responding to change over following a plan.
- Iterative Development
- Building in short, repeated cycles that each add value and gather feedback, enabling course correction.
- Incremental Delivery
- Delivering working slices of the product over time rather than everything at the end.
- Empiricism
- Making decisions based on observation and evidence from working software through transparency, inspection, and adaptation.
- Agile vs. Waterfall
- Waterfall completes phases sequentially; Agile delivers value iteratively with continuous feedback, reducing risk and accommodating change.
Scrum
- Scrum
- The most widely used Agile framework: small cross-functional teams deliver value in fixed-length sprints, guided by defined roles, events, and artifacts.
- Sprint
- A fixed timebox (typically 1–4 weeks) in which the team plans, builds, tests, and delivers a potentially releasable increment.
- Product Owner
- The role accountable for maximizing value by owning and prioritizing the product backlog and representing stakeholders.
- Scrum Master
- A servant-leader who facilitates Scrum, coaches the team, and removes impediments.
- Development Team
- The cross-functional group that does the work of delivering a done increment each sprint.
- Sprint Planning
- The event where the team selects backlog items and defines a plan and goal for the sprint.
- Daily Scrum
- A short daily synchronization where the team coordinates work toward the sprint goal and surfaces impediments.
- Sprint Review
- An event where the team demonstrates the increment and gathers stakeholder feedback.
- Sprint Retrospective
- A reflection where the team identifies improvements to its process for the next sprint.
- Product Backlog
- The single, prioritized list of everything that might be needed in the product, owned by the Product Owner.
- Increment
- The sum of completed backlog items that is potentially releasable at the end of a sprint.
Stories & Estimation
- User Story
- A short, user-focused description of functionality: 'As a <role>, I want <goal> so that <benefit>.'
- Acceptance Criteria
- Conditions that define when a story is complete and correct, guiding development and testing.
- Story Points
- A relative measure of size combining effort, complexity, and uncertainty, rather than absolute time.
- Planning Poker
- A consensus estimation technique where members reveal estimates simultaneously and discuss differences.
- Velocity
- The average story points a team completes per sprint, used to forecast future capacity.
Kanban
- Kanban
- A flow-based method that visualizes work, limits work in process, and manages flow to improve delivery.
- Limiting WIP
- Capping the amount of work in progress to reduce multitasking, expose bottlenecks, and improve throughput.
- Kanban Board
- A visual board showing work items moving through stages, making flow and bottlenecks visible.
Quality & Delivery
- Built-In Quality
- Practices like test-first, continuous integration, and a strong Definition of Done that keep quality high throughout.
- Continuous Improvement
- Regularly reflecting and adjusting so the team gets measurably better over time.