click to reveal definition
click to flip back
You know 0 of 24 cards in current set.
Ready to get certified?
Get CertifiedNeed this expertise applied inside your organization?
Explore Our ServicesFull Glossary
Agile Principles
- Agile
- An iterative, incremental approach that delivers value early and often and responds to change through feedback and collaboration.
- Agile Manifesto
- Four values and twelve principles that prioritize individuals, working software, collaboration, and responding to change.
- Empiricism
- Making decisions from observation and evidence via transparency, inspection, and adaptation.
- Iterative & Incremental
- Delivering value in short cycles that each add working functionality and gather feedback.
Scrum Framework
- Scrum
- A lightweight framework where cross-functional teams deliver value in fixed-length sprints, defined by roles, events, and artifacts.
- Scrum Pillars
- Transparency, inspection, and adaptation — the empirical pillars that Scrum is built upon.
- Scrum Values
- Commitment, courage, focus, openness, and respect — behaviors that make Scrum effective.
Roles
- Product Owner
- Accountable for maximizing value by owning and ordering the product backlog and representing stakeholders.
- Scrum Master
- A servant leader who facilitates Scrum, coaches the team, and removes impediments.
- Developers
- The cross-functional team members who do the work of delivering a done increment each sprint.
Events
- Sprint
- A fixed timebox (1–4 weeks) that contains all the work and events needed to produce a done increment.
- Sprint Planning
- The event where the team defines a sprint goal and selects and plans the work to achieve it.
- Daily Scrum
- A short daily synchronization to coordinate toward the sprint goal and surface impediments.
- Sprint Review
- A working session where the team demonstrates the increment and gathers feedback.
- Sprint Retrospective
- A reflection where the team identifies improvements to its process for the next sprint.
Artifacts
- Product Backlog
- The single, ordered list of everything that might be needed, owned by the Product Owner.
- Sprint Backlog
- The sprint goal, selected items, and plan the developers own for the sprint.
- Increment
- The sum of completed backlog items meeting the Definition of Done, potentially releasable.
- Definition of Done
- A shared checklist of quality criteria work must meet to be considered complete.
Practices
- User Stories
- User-focused descriptions of functionality with acceptance criteria that guide delivery.
- Relative Estimation
- Sizing work by comparison using story points rather than absolute time, often via planning poker.
- Velocity
- The average points a team completes per sprint, used to forecast capacity.
- Backlog Refinement
- Ongoing detailing, estimating, and ordering so the top of the backlog is ready.
- Built-In Quality
- Practices like test-first and continuous integration that keep quality high throughout the sprint.