EXIN Agile Scrum Foundation flashcards
EXIN Agile Scrum Foundation · Build recall with a focused review session.
33 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Empirical process control
- A process model in which decisions are based on observation of actual results rather than on predefined plans. Scrum implements it through transparency, inspection, and adaptation.
- Three pillars of Scrum
- Transparency, inspection, and adaptation. Transparency makes work visible, inspection checks the artifacts and progress, and adaptation adjusts process or product when results deviate.
- Agile Manifesto values
- Four preference statements: individuals and interactions, working software, customer collaboration, and responding to change, each preferred over its counterpart while the counterpart retains value.
- Scrum values
- Commitment, focus, openness, respect, and courage. They describe expected behavior that supports the three empirical pillars and trust within the Scrum Team.
- Definition of Done
- A formal description of the state of the Increment when it meets the quality measures required for the product. It is the commitment attached to the Increment artifact.
- Product Goal
- A long-term objective for the Scrum Team that describes a future state of the product. It lives in the Product Backlog and is the commitment for that artifact.
- Sprint Goal
- A single objective for the Sprint that gives the Developers focus and flexibility on scope. It is the commitment attached to the Sprint Backlog.
- Product Owner accountability
- Maximizing product value by ordering the Product Backlog, making it transparent and understood, and deciding what to build next. One person, not a committee.
- Scrum Master accountability
- Establishing Scrum as described and helping the Scrum Team and organization improve its effectiveness. The role has influence, not line authority over team members.
- Scrum Team size
- Typically ten or fewer people, comprising one Product Owner, one Scrum Master, and Developers. Larger groups should form multiple cohesive Scrum Teams on the same product.
- Sprint timebox
- A fixed length of one month or less. A new Sprint starts immediately after the previous one ends, and scope may be clarified but not changed arbitrarily.
- Sprint Planning timebox
- A maximum of eight hours for a one-month Sprint, shorter for shorter Sprints. It addresses why the Sprint is valuable, what can be done, and how.
- Daily Scrum timebox
- A 15-minute event for the Developers, held at the same time and place each working day, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
- Sprint Review timebox
- A maximum of four hours for a one-month Sprint. The Scrum Team and stakeholders inspect the Increment and collaborate on what to do next.
- Sprint Retrospective timebox
- A maximum of three hours for a one-month Sprint. The team inspects individuals, interactions, processes, tools, and the Definition of Done to plan improvements.
- Sprint cancellation
- Only the Product Owner may cancel a Sprint, and only when the Sprint Goal becomes obsolete. Completed items are reviewed and the backlog is re-planned.
- Product Backlog
- An emergent, ordered list of what is needed to improve the product. It is the single source of work for the Scrum Team and is continuously refined.
- Sprint Backlog
- A plan by and for the Developers, composed of the Sprint Goal, the selected Product Backlog items, and the plan to deliver the Increment. Updated daily.
- Increment
- A concrete stepping stone toward the Product Goal. Each Increment is additive to prior ones, verified against the Definition of Done, and usable.
- Story points
- A relative unit of estimate reflecting effort, complexity, and uncertainty together. Values are team-specific and should not be compared across teams.
- Planning Poker
- A consensus estimation technique in which estimators reveal cards simultaneously, discuss the highest and lowest estimates, and re-vote until the team converges.
- Velocity
- The sum of story points of backlog items that met the Definition of Done in a Sprint. Use a multi-Sprint average to forecast future capacity.
- Velocity forecast formula
- Expected Sprints ≈ remaining backlog size ÷ average velocity. The result is a probabilistic forecast that must be revisited as the backlog and team change.
- INVEST criteria
- A quality heuristic for user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable. Items failing it are split or clarified before selection.
- User story format
- As a role, I want a goal so that a benefit. It captures the need and its value, leaving detailed conversation and confirmation to the team.
- Three-point estimation
- A weighted estimate using optimistic, most likely, and pessimistic values: expected = (O + 4M + P) ÷ 6. It makes uncertainty explicit in numeric planning.
- Spike
- A timeboxed investigation to gain knowledge or reduce uncertainty before estimating or building. Its output is learning, not shippable product functionality.
- Burndown versus burnup
- A burndown shows remaining work trending to zero within a Sprint. A burnup shows completed work against total scope, making scope changes visible.
- Backlog refinement
- Ongoing decomposition and sizing of Product Backlog items to prepare them for future Sprints. It is not one of the five formal Scrum events.
- Stakeholder engagement point
- The Sprint Review is the formal recurring touchpoint where stakeholders inspect the Increment and provide feedback that shapes the Product Backlog.
- Self-managing team
- A team that internally decides who does what, when, and how. The Scrum Master coaches the team but does not assign tasks or dictate technical solutions.
- Impediment escalation
- Impediments within team authority are solved by the team; those caused by organizational policy or tooling are raised by the Scrum Master to management.
- Scaling constraint
- Multiple Scrum Teams on one product need one Product Owner, one Product Backlog, a shared Definition of Done, and explicit dependency management to integrate continuously.