Examius
🇺🇸 Certified ScrumMaster (CSM) · flashcards
Certified ScrumMaster (CSM) Scrum Accountabilities and Team Structure Flashcards
51 question-and-answer cards covering Scrum Accountabilities and Team Structure as it is examined in Certified ScrumMaster (CSM). 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.
24 sample cards from the Scrum Accountabilities and Team Structure deck
Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.
How does team composition relate to delivering value each Sprint?
A Scrum Team must include all the competencies needed (cross-functionality) so it can turn Product Backlog items into a Done Increment within a single Sprint without external dependencies.
If a product needs more than 10 people, how should work be organized in Scrum?
Form multiple Scrum Teams, each cohesive and small, all sharing the same Product Goal, Product Backlog, and Product Owner, rather than enlarging a single team.
What does the Scrum Master remove to help the team make progress?
Impediments — obstacles that slow or block the team's progress toward the Sprint Goal.
How is accountability for the Increment shared versus individual?
The Developers as a group are accountable for the Increment; Scrum assigns no individual sub-accountabilities for parts of it, reinforcing collective ownership.
What is the relationship between the Scrum Master's authority and the team's self-management?
The Scrum Master has no command authority over the team; they enable self-management by coaching and removing impediments, so the team itself decides how to work.
Why is a Scrum Team described as 'small enough to remain nimble but large enough to complete significant work'?
This balance keeps communication overhead low and cohesion high (nimble) while ensuring the team has enough capacity and skills to deliver a meaningful Increment each Sprint.
How does the Scrum Master serve the organization regarding stakeholders and teams?
By removing barriers between stakeholders and Scrum Teams so that collaboration and transparency improve across organizational boundaries.
What technique help does the Scrum Master provide the Product Owner for the backlog?
Helping find effective techniques for Product Goal definition and Product Backlog management, and helping the team understand the need for clear and concise Product Backlog items.
Who creates the Sprint Backlog, and what does that represent?
The Developers create the Sprint Backlog. It is their plan for the Sprint — the Sprint Goal, the selected Product Backlog items, and the actionable plan for delivering the Increment.
How does the Definition of Done relate to Developers' accountability?
Developers are accountable for instilling quality by adhering to the Definition of Done; it defines the state an Increment must reach to be considered complete and releasable.
Daily, what do Developers adapt and toward what?
They adapt their plan (the Sprint Backlog) each day toward the Sprint Goal, inspecting progress and adjusting work as needed.
Contrast the Product Owner's and Developers' primary focus.
The Product Owner focuses on maximizing value — what to build and in what order (the 'what/why'). The Developers focus on creating a quality Increment — how to build it (the 'how').
Contrast the Scrum Master's service to the team versus the organization.
To the team, the Scrum Master coaches self-management, removes impediments, and ensures effective events. To the organization, the Scrum Master leads, trains, and coaches Scrum adoption and removes inter-team/stakeholder barriers.
Is 'Scrum Master' a management position over the team? Explain.
No. The Scrum Master is an accountability focused on team and organizational effectiveness through servant-leadership and coaching, not a hierarchical manager with authority to direct the Developers' work.
What makes the Scrum Team 'cohesive'?
All members focus on a single Product Goal, share collective accountability, and operate without sub-teams or hierarchies, working together as one unit.
How does the Product Owner ensure the Product Backlog is effective for the team?
By ensuring it is transparent, visible, and understood — clearly communicated and ordered so the Developers know what to work on next and why.
What is meant by 'empirical' product planning that the Scrum Master helps establish?
Planning based on transparency, inspection, and adaptation using actual evidence and outcomes, rather than detailed up-front predictive plans, to manage complex work.
Who can change the order of Product Backlog items?
Only the Product Owner. Others may try to influence the ordering, but the authority and accountability for ordering rest solely with the Product Owner.
What is the single shared objective that keeps a multi-team product aligned in Scrum?
The Product Goal — all Scrum Teams working on the same product share one Product Goal, one Product Backlog, and one Product Owner.
How do the three accountabilities together fulfill the Scrum Team's purpose?
The Product Owner maximizes value, the Developers build a quality Increment, and the Scrum Master ensures effectiveness — together delivering valuable, usable Increments toward the Product Goal each Sprint.
Why does Scrum avoid assigning individual titles like 'tester' or 'architect' within the team?
To reinforce cross-functionality and shared accountability; all members are 'Developers' committed to the Increment, preventing silos and ensuring whole-team responsibility for quality.
What does the Scrum Master do for Scrum events?
Ensures that all Scrum events take place, are positive and productive, and are kept within their time-boxes (facilitating as needed).
How does stakeholder representation flow into the product in Scrum?
Stakeholders express needs to the Product Owner, who represents those needs as ordered Product Backlog items; stakeholders also inspect the Increment and provide feedback at the Sprint Review.
What is the core principle behind 'accountability to each other' in a Scrum Team?
Self-management is sustained through mutual, peer-to-peer accountability: members hold one another responsible as professionals for commitments, quality, and behavior, rather than relying on external supervision.
What this deck covers
The Scrum Accountabilities and Team Structure deck follows the Certified ScrumMaster (CSM) Scrum Accountabilities and Team Structure syllabus — 4 chapters and 13 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 12.8 cards per chapter.
Answers are written to be recallable, not just readable — averaging about 167 characters, which is long enough to carry the reasoning and short enough to say out loud.
A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.
Scrum Accountabilities and Team Structure flashcards FAQ
How many Scrum Accountabilities and Team Structure flashcards are in this Certified ScrumMaster (CSM) deck?
51 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.
Are these Certified ScrumMaster (CSM) flashcards free?
Yes. The preview here is free to read with no signup, and the full 51-card deck is free inside the Examius app.
What do the Scrum Accountabilities and Team Structure cards cover?
They follow the Certified ScrumMaster (CSM) Scrum Accountabilities and Team Structure syllabus — 4 chapters and 13 topics — so the questions track what is actually examinable.
How should I use these flashcards?
Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.