PSM flashcards
PSM · 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
- A theory that knowledge comes from experience and decisions are based on observation. In Scrum, it relies on transparency, inspection, and adaptation to manage complex work.
- Scrum Values
- Commitment, Focus, Openness, Respect, and Courage. These values guide behavior and help the Scrum Team make decisions that support empiricism and trust.
- Transparency
- The empirical pillar that makes work and state visible to those responsible for outcomes. Without transparency, inspection is misleading and adaptation is ineffective.
- Scrum Team
- A self-managing, cross-functional group of 10 or fewer people consisting of one Scrum Master, one Product Owner, and Developers, focused on delivering value each Sprint.
- Product Owner
- Accountable for maximizing product value by managing the Product Backlog, ordering items, and communicating the Product Goal. May delegate work but remains accountable.
- Scrum Master
- Accountable for establishing Scrum as defined in the Scrum Guide. Serves the Scrum Team and organization by coaching, facilitating, and removing impediments.
- Developers
- Members of the Scrum Team accountable for creating a usable Increment each Sprint, adapting the Sprint Backlog daily, and holding each other accountable for quality.
- Sprint
- A fixed-length event of one month or less that serves as a container for all other Scrum events. A new Sprint starts immediately after the previous one ends.
- Sprint Planning
- A timeboxed event (max 8 hours for a one-month Sprint) where the Scrum Team defines the Sprint Goal, selects Product Backlog items, and plans how to deliver them.
- Daily Scrum
- A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Held at the same time and place each day.
- Sprint Review
- A timeboxed event (max 4 hours for a one-month Sprint) to inspect the Increment, collaborate with stakeholders, and update the Product Backlog based on feedback.
- Sprint Retrospective
- A timeboxed event (max 3 hours for a one-month Sprint) where the Scrum Team inspects individuals, interactions, processes, tools, and Definition of Done to improve.
- 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, with the Product Goal as its commitment.
- Sprint Backlog
- Composed of the Sprint Goal (why), selected Product Backlog items (what), and a plan for delivering the Increment (how). It is updated as more is learned.
- Increment
- A concrete stepping stone toward the Product Goal. It must be usable to provide value and meets the Definition of Done. Multiple Increments may exist within a Sprint.
- Definition of Done
- A formal description of the state of the Increment when it meets the quality measures required for the product. Work not meeting it cannot be released.
- Product Goal
- A long-term objective for the Scrum Team that describes a future state of the product. It is the commitment for the Product Backlog and provides direction.
- Self-Managing Team
- A team that internally decides who does what, when, and how. It operates within organizational boundaries and Scrum rules, supported by trust and clear goals.
- Cross-Functional Team
- A team with all the skills necessary to create value each Sprint. Cross-functionality and self-management are core characteristics of the Scrum Team.
- Facilitation
- Designing and guiding group processes to achieve a clear purpose while remaining neutral on content. It ensures participation, transparency, and productive outcomes.
- Fist of Five
- A facilitation technique where participants show fingers (0–5) to indicate agreement level. It quickly reveals consensus and areas needing discussion.
- Coaching
- A collaborative, reflective process that helps individuals and teams unlock potential. It uses powerful questions, active listening, and feedback rather than giving advice.
- Active Listening
- A coaching skill involving full attention, paraphrasing, and summarizing to understand the speaker's message and emotions. It builds trust and clarity.
- Forecasting
- Using historical data and empirical evidence to predict future delivery probabilistically. It is not a guarantee and should be updated as more is learned.
- Velocity
- A trailing indicator showing the average amount of work completed per Sprint. Use a range rather than a single number for forecasting.
- Little's Law
- A formula stating average cycle time equals work in process divided by throughput. Reducing WIP improves cycle time and predictability.
- Product Value
- The measure of outcomes that benefit customers and the organization. It is assessed through feedback, usage, and stakeholder input, not just output.
- Value Maximization
- The Product Owner's accountability to order the Product Backlog and make trade-offs that deliver the most valuable outcomes for customers and the organization.
- Product Backlog Refinement
- The ongoing act of breaking down and further defining Product Backlog items to increase clarity and readiness for upcoming Sprints. It is not a formal Scrum event.
- Backlog Ordering
- The Product Owner's decision on the sequence of Product Backlog items to maximize value. Items at the top are typically clearer and more detailed.
- Stakeholders
- People with an interest in the product, such as customers, users, and managers. The Product Owner engages them to understand needs and priorities.
- Customer Feedback
- Input from customers about the product, often gathered through usage and direct interaction. It informs Product Backlog ordering and value assessment.