PremierAgile

Almost there, CSM aspirants! In previous posts, we discussed Scrum's basic ideals, roles, and events. Today, we'll wrap up our series with a look at Scrum Artifacts, which are the informational items that serve as the foundation for transparency and lead the Scrum Team throughout the project's lifetime.

Scrum provides three key artifacts that collect and communicate critical information about Scrum projects. A thorough understanding of these items is essential for succeeding in your CSM exam and ensuring successful Scrum deployment.

Let's assess your knowledge with some sample questions:

1. An Increment is:

• The user interface of a product.
• Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together.
• An elapsed time that the Scrum Team spends on creating the product.
• That satisfies the end User.

2. The following statements are true about a Product Backlog:

• Only Product Owner can write and prioritize Product Backlog items.
• Only Product Owner and Users can write Product Backlog items, and Product Owner will prioritize Product Backlog items.
• Only Product Owner, Scrum Master and Users can write Product Backlog items, and Product Owner will prioritize Product Backlog items.
• Anyone can write Product Backlog items, and the Product Owner has the authority to prioritize.

3. ------ are present in the Sprint Backlog and are normally estimated in hours.

• Stories.
• User cases.
• Features.
• Tasks.

4. The following is true regarding Definition of Done:

• A formal description of the state of the Increment when it meets the quality measures.
• Creates transparency by providing everyone a shared understanding.
• Developers are required to conform to the Definition of Done.
• All of the above.

5. The Product Backlog is usually ordered by:

• Ordered by Risk. Low risk items to be on top and high - risk items at the bottom.
• Ordered by complexity. Less complex items are on top and high complex items at the bottom.
• Effort estimation.
• Business Value.

6. Product Backlog can be modified during:

• During Product Backlog Refinement.
• During Sprint Review.
• During market adjustments.
• All of the above.

7. A Sprint Backlog's plan can be adjusted:

• As and when a Developers want to work on an interesting user story.
• Only during the first half of the Sprint.
• As long as the Sprint Goal is intact.
• Only during the Sprint Planning meeting.

8. When should an Increment(s) be released?

• When the Developers determine that the Increment is done.
• When the Product Owner determines that the Increment is done.
• When the Product Owner determines the Increment provides value to business users.
• When the Scrum Master says there are no impediments for the product release.

9. Who can modify the Sprint Backlog - Plan?

• Developers only.
• Developers and Product Owner.
• Developers and Scrum Master.
• Scrum Team.

10. The following Scrum artifacts evolve during the course of time:

• Product Backlog.
• Sprint Backlog.
• Both.
• None of the above.

11. A Product Increment must be:

• End to end system.
• Usable.
• Detailed enough to understand users.
• Partial system that can store user data.

12. The following serves as a commitment to measure progress:

• For the Product Backlog it is the Product Goal.
• For the Sprint Backlog it is the Sprint Goal.
• For the Increment it is the Definition of Done.
• All of the above.

Congratulations!

You've successfully completed this series on CSM exam preparation! We've covered a range of essential Scrum concepts, including Agile Manifesto, Scrum theory, values, roles, events, and artifacts.

Remember: Our Scrum experts are always available to answer your questions and provide additional support on your CSM certification journey. Feel free to reach out and leverage their expertise!