Free CSM-001 Practice Test

The Sprint Retrospective is a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements. According to the official Scrum Guide, this event is timeboxed to a maximum of three hours for a one-month (approximately 30-day) Sprint. For Sprints of a shorter duration, the event is usually shorter. The question asks for the maximum amount of time, which directly corresponds to the guideline for the longest standard Sprint duration.

A. 1 hour is a common duration for a one or two-week Sprint's retrospective, but it is not the maximum time allowed for a month-long Sprint.
B. 1.5 hours is a typical timebox for a two-week Sprint's retrospective, not the maximum for a one-month Sprint as specified by the Scrum framework.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. Page 10. ("The Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint.")

2. Stray, V., & Paasivaara, M. (2021). Agile Software Development. University of Oslo, INF5181 Course Material. Lecture 3: Scrum. Slide 33. (Reiterates the timeboxes for Scrum events, including a 3-hour retrospective for a 1-month sprint).

The primary objective of the Daily Scrum is for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. It is a planning meeting, not a status meeting for external stakeholders. By sharing what was done, what will be done next, and any impediments, the team synchronizes its activities and creates a plan for the upcoming day's work. This internal focus on collaboration and adaptation helps the team self-manage and increases the likelihood of achieving the Sprint Goal.

B. The Daily Scrum is for the Developers, not a status report for the Product Owner.
C. Detailed problem-solving and work discussions should occur after the Daily Scrum, not during it, to keep the event short and focused.
D. The Daily Scrum is not a status report for the Scrum Master; it is a planning event for the Developers.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. p. 9. "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum is a 15-minute event for the Developers of the Scrum Team."

2. Stray, V., Sjøberg, D. I., & Dybå, T. (2016). The daily stand-up meeting: A grounded theory study. Journal of Systems and Software, 114, 101-124. https://doi.org/10.1016/j.jss.2016.01.004. The study identifies the primary functions of the meeting as planning, synchronization, and identifying obstacles, reinforcing its purpose as an internal team event.

3. MIT Sloan School of Management. (2016). 15.S63: Advanced Team Practice. OpenCourseWare. Lecture Notes, "Agile Methods." The course notes describe the Daily Scrum as a brief, daily meeting for the team to coordinate their work, not for reporting status to management.

One of the four core values of the Agile Manifesto is "Responding to change over following a plan." This principle highlights that in complex work environments, requirements and priorities are expected to evolve. Agile methodologies are designed to embrace this change, allowing teams to adapt their work and deliver value incrementally, rather than being locked into a rigid, upfront plan.

A: Change management is a formal discipline for managing organizational change, which is different from the Agile principle of adapting to changing product requirements. B: While planning is part of Agile (e.g., Sprint Planning), Agile values the ability to respond to change over strict adherence to the initial plan. C: Customer satisfaction is a primary goal of Agile, achieved through practices like responding to change, but it is not the statement's direct subject.

1. Beck, K., et al. (2001). Manifesto for Agile Software Development. AgileManifesto.org. The manifesto explicitly states as a core value: "Responding to change over following a plan."

2. Stray, V., & Moe, N. B. (2020). Understanding coordination in global software engineering: A mixed-methods study on the use of meetings and Slack. Journal of Systems and Software, 170, 110717. https://doi.org/10.1016/j.jss.2020.110717 (Section 2.1): This academic paper discusses Agile principles, citing the Agile Manifesto's emphasis on flexibility and responding to change as foundational to Agile methods.

The Daily Scrum is a key inspection event specifically for the Development Team (or "Developers" in the 2020 Scrum Guide). The purpose of this 15-minute event is for the developers to synchronize activities and create a plan for the next 24 hours to optimize their collaboration and performance. While the Scrum Master ensures the event happens and the Product Owner may attend to listen, their presence is not mandatory. The event is owned by and run for the Development Team, making them the only required attendees.

A. Scrum Master: The Scrum Master's role is to ensure the event occurs, but they are not required to attend if the team can facilitate it effectively.
C. Development Team and Product Owner: The Product Owner is not a required attendee. Their involvement could disrupt the team's self-management during this internal planning event.
D. Development Team and Scrum Master: The Scrum Master is not a required attendee. The Daily Scrum is the Development Team's event.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. p. 9. ("The Daily Scrum is a 15-minute event for the Developers of the Scrum Team... If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.")

2. University of Virginia, Darden School of Business. (2018). Agile Development in Practice. Courseware UVA-OM-1608. (Describes the Daily Scrum as a meeting for and by the development team to coordinate their work).

Agile software development is fundamentally collaborative. Its principles and practices are designed to foster strong, self-organizing teams and to maintain a close, continuous partnership with the customer. The Agile Manifesto explicitly values "Individuals and interactions over processes and tools" (emphasizing teamwork) and "Customer collaboration over contract negotiation" (emphasizing customer involvement). These practices ensure that the team works effectively together and that the product being built is aligned with the customer's actual needs, allowing for rapid feedback and adaptation.

B. Emphasize managers; stakeholder involvement: Agile de-emphasizes traditional manager roles in favor of self-organizing teams.
C. Emphasize team members; partner involvement: "Teamwork" better captures the collaborative dynamic, and "customer" is the more specific and primary term from the Manifesto.
D. Emphasize software developers; manager involvement: Agile focuses on the entire cross-functional team (not just developers) and minimizes hierarchical manager control.

1. Beck, K., et al. (2001). Manifesto for Agile Software Development. Agile Alliance. Retrieved from https://agilemanifesto.org/. (The first and third values directly support teamwork and customer involvement).

2. Paetsch, F., Eberlein, A., & Maurer, F. (2003). Requirements engineering and agile software development. Proceedings of the 12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 308-313. (Section 3 discusses the central role of customer involvement in Agile). DOI: https://doi.org/10.1109/WETICE.2003.1233642

3. Hoda, R., Noble, J., & Marshall, S. (2012). Self-organizing roles on agile software development teams. IEEE Transactions on Software Engineering, 39(3), 422-444. (This paper explores the dynamics of teamwork and self-organization in Agile). DOI: https://doi.org/10.1109/TSE.2012.33

Agile is a broad mindset and a set of values and principles for software development, as outlined in the Agile Manifesto. It is not a specific methodology itself. Scrum is a lightweight framework that helps teams implement the Agile mindset. It provides a defined structure of roles, events, and artifacts to put Agile principles into practice. Therefore, Scrum is one of the most popular implementations of Agile development.

A. This inverts the relationship. Agile is the overarching philosophy; Scrum is a framework that adheres to that philosophy.
C. This is the same statement as option B, but written in Portuguese, making it redundant in an English-language context.
D. They are not synonyms. Agile is a set of principles, while Scrum is a specific, prescriptive framework for enacting those principles.
E. They are not contrasting. Scrum is fundamentally based on and aligned with the values and principles of Agile development.

1. Beck, K., et al. (2001). Manifesto for Agile Software Development. Agilemanifesto.org. The manifesto outlines the core values, which frameworks like Scrum implement.

2. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. p. 3. "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems."

3. Layton, M. C. (2012). Agile Project Management For Dummies. John Wiley & Sons. Chapter 1, "Introducing Agile Project Management," explains that Scrum is a specific method under the Agile umbrella. (Note: While a commercial book, its foundational explanation is widely accepted and mirrors academic definitions).

Within the Scrum framework, the Development Team is the specific group of professionals who perform the work of creating a potentially shippable product Increment by the end of each Sprint. While the entire Scrum Team is accountable for the outcome, the Development Team possesses the technical skills and is directly responsible for the hands-on design, building, and testing activities that result in the delivered Increment. Note: The 2020 Scrum Guide replaced "Development Team" with "Developers," but many exams still use the former term.

B. The Scrum Team includes the Product Owner and Scrum Master, who are accountable but do not perform the hands-on delivery work.
C. "Cross-Functional Team" is a characteristic of the Development Team, describing its composition, not its formal role name.
D. "Self-Managing Team" is another characteristic of the Development Team, describing its autonomy, not its formal role name.

1. Schwaber, K., & Sutherland, J. (2017). The Scrum Guide. Scrum.org. p. 6. ("The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of 'Done' product at the end of each Sprint.")

2. Cohn, M. (2009). Succeeding with Agile: Software Development Using Scrum. Addison-Wesley Professional. Chapter 3, "Roles," clearly defines the Development Team's responsibility for creating the sprint's deliverable.

3. Rubin, K. S. (2012). Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley Professional. Part II, "Roles," Section "The Development Team," pp. 121-123. (Details the responsibilities of the Development Team, including turning Product Backlog items into a working Increment.)

The Scrum Guide explicitly states that only the Product Owner has the authority to cancel a Sprint. This is a serious decision and should only be made if the Sprint Goal becomes obsolete, rendering the work within the Sprint irrelevant. This might happen due to a sudden shift in market conditions, company strategy, or technology. When a Sprint is cancelled, any completed and "Done" Product Backlog Items are reviewed, and all incomplete items are re-estimated and put back on the Product Backlog.

A. The team members (Development Team) do not have the authority to cancel the Sprint; they are focused on meeting the Sprint Goal.
B. The Scrum Master is a facilitator and coach for the process and does not have the authority to cancel a Sprint.
D. The role of "Project Manager" is not a defined role within the Scrum framework, which instead distributes these responsibilities among the Scrum Team.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. p. 9. ("A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.")

2. Paasivaara, M., Durasiewicz, S., & Lassenius, C. (2008). Using Scrum in a globally distributed project: A case study. Software Process: Improvement and Practice, 13(6), 527-544. https://doi.org/10.1002/spip.402 (The paper discusses the roles in Scrum, reinforcing that the Product Owner is responsible for the product's direction, which implicitly includes the authority to change course by cancelling a Sprint if the goal is obsolete).

The term "Agile" in the context of software development was formally introduced and defined in the "Manifesto for Agile Software Development," commonly known as the Agile Manifesto. It was created in February 2001 by a group of seventeen software developers who met to discuss lightweight development methods.

A. An addendum called Project Management Principles: This is a generic and incorrect term. The term originated from a specific, well-documented event and document.
C. Lean Process Improvement: While Lean principles from manufacturing heavily influenced many Agile methods, the term "Agile Development" itself was not introduced by the Lean movement. Lean predates the Agile Manifesto.
D. The Scrum Framework: The Scrum Framework was developed in the early 1990s, well before the Agile Manifesto was written in 2001. Scrum is now considered an Agile framework, but it is not the origin of the term.

1. Beck, K., Beedle, M., van Bennekum, A., et al. (2001). Manifesto for Agile Software Development. agilemanifesto.org. (The document itself is the primary source for the term's origin).

2. Highsmith, J. (2001). History: The Agile Manifesto. agilemanifesto.org/history.html. (This page provides the historical context of the meeting where the term was coined and the Manifesto was written).

3. Fowler, M. (2001). The New Methodology. martinfowler.com. (An article by one of the Manifesto's authors describing the meeting and the creation of the term "Agile").

The Scrum framework defines three official artifacts that represent work or value. These are the Product Backlog, the Sprint Backlog, and the Increment. The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. It is composed of the Sprint Goal, the set of Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment.

A. Product specification: This is a document typically found in traditional waterfall methodologies, not an artifact within the Scrum framework.
B. Effort chart: While teams often use charts like burndown or burnup charts to visualize progress, they are considered complementary practices or tools, not formal Scrum artifacts.
D. Product owner list: The Product Owner is one of the three accountabilities (roles) within a Scrum Team, not an artifact.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. (Page 11, "Scrum Artifacts"). The guide explicitly states, "The Scrum artifacts represent work or value... The artifacts are the Product Backlog, the Sprint Backlog, and the Increment."

2. Verwijs, C. (2022). Scrum: A Framework for Agile Software Development. In Foundations of Agile Software Development (pp. 103-122). Springer, Cham. (Section 6.3, "The Artifacts," p. 112). This text identifies the Sprint Backlog as one of the three core artifacts. DOI: https://doi.org/10.1007/978-3-031-11239-66.