サンプル問題 1: Every Scrum Team should have: (Choose the best answer)
A: The competencies and skills needed to deliver a Done Increment in a Sprint.
B: At least one representative from each major software engineering discipline (like QA, Dev, UX).
C: One Lead Developer and no more than eight other members.
正解:A
Explanation: The Scrum Guide emphasizes that a Scrum Team must be cross-functional, meaning it has all the competencies and skills necessary to create a "Done" Increment within a Sprint without relying on external resources. Option A aligns directly with this principle: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers... They are cross-functional, meaning the members have all the skills necessary to create value each Sprint." Option B, while suggesting a structured representation from disciplines, is too prescriptive and not a Scrum requirement―Scrum does not mandate specific roles like QA or UX within the Developers. Option C imposes a rigid team structure (one Lead Developer and a maximum of eight others), which contradicts Scrum’s flexibility in team composition (typically 10 or fewer total, but no specific roles or limits beyond that are mandated). Thus, A is the best answer, focusing on capability rather than structure. Reference: Scrum Guide (2020), Section: "The Scrum Team."
サンプル問題 2: What three factors are best considered when establishing the Sprint length? (Choose the best three answers)
A: The ability to go to market with a product release.
B: Sprints must have the same length throughout an organization.
C: The frequency at which team formation can be changed.
D: The level of uncertainty over the technology to be used.
E: The risk of being disconnected from the stakeholders.
正解:A, D, E
Explanation: Sprint length in Scrum is a critical decision that impacts the team’s ability to deliver value and adapt. The Scrum Guide states that Sprints are fixed in length (typically one month or less) to create consistency and enable regular inspection and adaptation. While it doesn’t explicitly list factors, practical application and Scrum principles suggest: A (The ability to go to market with a product release): Shorter Sprints allow faster feedback and releases, aligning with Scrum’s focus on delivering value frequently. D (The level of uncertainty over the technology to be used): High uncertainty may warrant shorter Sprints to mitigate risk and validate assumptions, a key aspect of empirical process control. E (The risk of being disconnected from the stakeholders): Shorter Sprints ensure frequent stakeholder engagement (e.g., via Sprint Reviews), reducing this risk. Option B is incorrect because Scrum does not require uniform Sprint lengths across an organization― each team can choose what works best. Option C is irrelevant, as team formation changes are not tied to Sprint length in Scrum. Thus, A, D, and E are the best factors. Reference: Scrum Guide (2020), Section: "Sprint."
サンプル問題 3: Which three of the following are true about Scrum? (Choose the best three answers)
A: Scrum is a methodology, where you can pick and choose which parts of Scrum you think will work for your environment.
B: Scrum is like traditional processes but with self-organization to replace Project Managers.
C: Scrum is a framework for developing and sustaining complex products.
D: Scrum is based on empirical process control theory.
E: Each component of Scrum serves a specific purpose and is essential to Scrum’s success and your usage of Scrum to develop complex products.
正解:C, D, E
Explanation: C: The Scrum Guide defines Scrum as "a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems." This is a core truth. D: Scrum’s foundation in empirical process control theory (transparency, inspection, adaptation) is explicitly stated in the Scrum Guide: "Scrum is founded on empiricism and lean thinking." E: The Scrum Guide emphasizes that "each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum." Altering components risks losing Scrum’s benefits. Option A is false―Scrum is a framework, not a methodology, and cherry-picking parts undermines its integrity. Option B misrepresents Scrum; it’s not a tweak on traditional processes but a distinct approach, and it doesn’t merely replace Project Managers with self-organization―it eliminates that role entirely. Thus, C, D, and E are correct. Reference: Scrum Guide (2020), Sections: "Scrum Definition," "Scrum Theory."