CSPO flashcards
CSPO · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Empiricism
- The Scrum theory that knowledge comes from experience and decisions are based on what is observed. It relies on transparency, inspection, and adaptation to manage complex work.
- Three pillars of Scrum
- Transparency, inspection, and adaptation. Transparency makes work visible; inspection checks progress toward goals; adaptation adjusts process or product when results deviate.
- Scrum values
- Commitment, focus, openness, respect, and courage. These five values guide the behavior of the Scrum Team and support the empirical pillars.
- Sprint
- A fixed-length event of one month or less that contains all other Scrum events. Each Sprint turns ideas into a usable Increment and has a consistent length.
- Sprint Planning
- The event that opens the Sprint. It establishes the Sprint Goal, selects backlog items, and plans how the work will be done, timeboxed to 8 hours for a one-month Sprint.
- Daily Scrum
- A 15-minute event for Developers held each working day. It inspects progress toward the Sprint Goal and adapts the Sprint Backlog; it is not a status meeting.
- Sprint Review
- A working session with stakeholders at the end of the Sprint. It inspects the Increment, discusses what changed, and may adapt the Product Backlog.
- Sprint Retrospective
- The final event of the Sprint. The Scrum Team inspects its process and plans improvements to quality and effectiveness, timeboxed to 3 hours for a one-month Sprint.
- Product Backlog
- An emergent, ordered list of everything needed to improve the product. It is the single source of work for the Scrum Team and its commitment is the Product Goal.
- Sprint Backlog
- The Sprint Goal, the selected Product Backlog items, and the plan for delivering them. It is a real-time picture of the Developers' work during the Sprint.
- Increment
- A concrete, usable stepping stone toward the Product Goal. Each Increment adds to prior Increments and must meet the Definition of Done to count as complete.
- Definition of Done
- A formal description of the state of the Increment when it meets the quality measures required for the product. It creates shared transparency about completed work.
- Scrum Master accountability
- Accountable for the Scrum Team's effectiveness. The Scrum Master coaches the team and organization in empiricism and removes impediments to progress.
- Developers accountability
- The people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint. They self-manage and decide how to do the work.
- Sprint cancellation
- Only the Product Owner may cancel a Sprint, and only when the Sprint Goal becomes obsolete. Cancellation is rare because it consumes resources and disrupts the team.
- Timeboxing
- Giving an event a maximum duration so it cannot expand indefinitely. Scrum timeboxes the Sprint, Planning, Daily Scrum, Review, and Retrospective.
- Product Owner accountability
- Accountable for maximizing product value. The Product Owner develops the Product Goal, orders the Product Backlog, and ensures it is transparent and understood.
- Product Goal
- A long-term objective for the Scrum Team and the commitment of the Product Backlog. Only one Product Goal is active at a time.
- Sprint Goal
- A single objective for the Sprint created during Sprint Planning. It guides the Developers and provides flexibility on scope while protecting focus.
- Product vision
- A description of the future state the product creates for customers. It is broader than the Product Goal and guides long-term backlog ordering.
- Backlog ordering
- The Product Owner's decision about item sequence, based on value, risk, dependencies, size, and learning. Ordering is the main signal of priority.
- Backlog refinement
- Ongoing work of adding detail, estimates, and order to Product Backlog items. It is not a formal Scrum event; the team decides how and when to do it.
- User story form
- A common backlog item format: As a role, I want a capability, so that I get a benefit. It keeps the user and value visible.
- Acceptance criteria
- Conditions a backlog item must satisfy to be accepted. They clarify intent and complement the Definition of Done, which applies to every Increment.
- Story splitting
- Dividing a large backlog item into smaller slices that still deliver value or learning. Slices may follow workflow steps, business rules, or data variations.
- Stakeholder mapping
- Identifying stakeholders by influence and interest to plan engagement. High-influence, high-interest groups need frequent collaboration; others need monitoring.
- Customer collaboration
- An Agile Manifesto value favoring working with customers over contract negotiation. Needs are discovered iteratively rather than fully specified up front.
- Responding to change
- An Agile Manifesto value favoring adaptation over rigid plans. The Product Backlog is reordered as learning arrives while the Sprint Goal provides stability.
- Working software
- An Agile Manifesto value that makes the usable Increment the primary measure of progress. Documentation supports value but does not replace a working product.
- Value vs. output
- Value is the outcome customers and the business receive; output is the volume of work produced. Product Owners order by value, using evidence such as usage data.
- Definition of Ready
- Not part of Scrum. If a team uses one, it is a local agreement and must not block backlog transparency or the Product Owner's ordering decisions.
- Forecast vs. commitment
- Developers forecast what they can deliver in a Sprint. Scope may be renegotiated with the Product Owner as learning occurs, while the Sprint Goal is protected.