PST flashcards
PST · 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 foundation holding that knowledge comes from experience and decisions are made on what is observed. It requires transparency, inspection, and adaptation to work.
- Lean thinking
- A Scrum foundation that reduces waste and focuses on essentials. It complements empiricism by keeping the process and artifacts as light as possible.
- Transparency
- The first empirical pillar: the emergent process, work, and artifacts are visible to those doing the work and those receiving it. Without it, inspection is misleading.
- Inspection
- The second empirical pillar: artifacts and progress toward agreed goals are checked frequently enough to detect unacceptable variances or problems early.
- Adaptation
- The third empirical pillar: the process or produced work is adjusted as soon as an unacceptable deviation is found, to minimize further deviation.
- Scrum values
- Commitment, Focus, Openness, Respect, and Courage. They give direction to the Scrum Team's work, actions, and behavior and support the empirical pillars.
- Complexity
- A condition where there are more unknowns than knowns and cause and effect are only clear in hindsight. Scrum is designed for work under this condition.
- Product Owner accountability
- Accountable for maximizing the value of the product resulting from the Scrum Team's work. Also accountable for effective Product Backlog management and ordering.
- Scrum Master accountability
- Accountable for establishing Scrum as defined in the Scrum Guide, for the Scrum Team's effectiveness, and for coaching the organization in its Scrum adoption.
- Developers accountability
- Accountable for creating any aspect of a usable Increment each Sprint, for the Sprint Backlog, and for instilling quality through the Definition of Done.
- Sprint
- The container event for all other events, one month or less in length. A new Sprint starts immediately after the previous one ends.
- Sprint Planning
- The event that initiates the Sprint by laying out the work. It addresses Why (Sprint Goal), What (items), and How (plan); timeboxed to eight hours for a one-month Sprint.
- Sprint Goal
- A concise, single objective for the Sprint that gives the Sprint Backlog flexibility in scope while keeping the team focused on a shared outcome.
- Daily Scrum
- A 15-minute event for Developers, held each working day at the same time and place, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
- Sprint Review
- A working session with stakeholders to inspect the Sprint outcome and determine future adaptations. Timeboxed to four hours for a one-month Sprint.
- Sprint Retrospective
- An event to plan ways to increase quality and effectiveness. Timeboxed to three hours for a one-month Sprint; top improvements may enter the Sprint Backlog.
- Definition of Done
- A formal description of the Increment's state when it meets the quality measures required for the product. If not organizational, the Scrum Team creates one.
- Product Goal
- A long-term target for the Scrum Team described in the Product Backlog. It guides ordering and is the commitment for that artifact.
- Increment
- A concrete stepping stone toward the Product Goal. Each Increment is additive, usable, and only counts as complete when it meets the Definition of Done.
- Facilitator stance
- Holding the process and container while leaving content ownership with the group. The facilitator surfaces disagreement rather than deciding for participants.
- 1-2-4-All
- A Liberating Structure where individuals reflect, then pairs, then fours, then the whole group converge. It maximizes participation before group convergence.
- What, So What, Now What
- A debrief structure: observations first, then meaning against theory, then a concrete change to try. Useful after simulations in Professional Scrum classes.
- 4C model
- Training From the Back of the Brain sequence: Connections, Concepts, Concrete Practice, Conclusions. It shifts class time from lecture toward practice.
- Flipped classroom
- Front-loading content exposure before live sessions so class time is used for practice, simulation, and debrief rather than lecture delivery.
- Psychological safety
- A classroom condition where participants can speak and be wrong without penalty. Structured turn-taking such as silent writing then pairs builds it.
- Professional Scrum Competencies
- Scrum.org's competency model with three focus areas: Understanding and Applying Scrum, Developing People and Teams, and Managing Products with Agility.
- Self-managing teams
- Teams that choose who does what, how, and on what work. The current Scrum Guide uses this term in place of self-organizing.
- Evidence-Based Management
- A Scrum.org framework for measuring value to improve decisions. It uses four Key Value Areas and their associated metrics.
- Key Value Areas
- Current Value, Unrealized Value, Time to Market, and Ability to Innovate. Each balances a competing concern and informs product decisions.
- PSM I assessment
- 80 multiple-choice questions in 60 minutes, passing score 85%. No course attendance is required; content follows the current Scrum Guide.
- PSM II assessment
- 30 questions in 90 minutes with an 85% passing score. It includes essay-style questions requiring written answers on Scrum application.
- Professional Scrum Trainer
- A Scrum.org-accredited trainer accountable for course fidelity. Requires the highest relevant assessment, a trainer process, and community participation.