Which of the following factors should you consider when setting the length of a Sprint’s timebox? Select all that apply.1 pointThe likelihood that the project will go over budgetHow much overhead—such as testing and review—goes into the delivery of the productThe expected frequency of changesHow much focused time the solution Developers need to build a Backlog item

Question 3How long is a typical Sprint’s timebox?1 pointBetween one and three daysBetween one and four weeksBetween two and three months

Question 4As a Product Owner, you set the initial Sprint duration the team has to work on their items. This refers to what Scrum concept? 1 pointTimeboxIntervalTime frameSchedule

The time box for the Sprint Planning event is?8 hours for a monthly sprint. For shorter sprints, it is usually shorter4 hoursWhenever it is doneMonthly

Sprint Retrospective is a Scrum event that has a timebox duration of three hours. (choose the BEST answer) Question 4 options: For a one-week Sprint, Sprint Retrospective's duration can be longer than three hours to get additional valuable feedback from the Scrum Team for future adaptation For a one-month Sprint, Sprint Retrospective's maximum duration is three hours For a one-week Sprint, Sprint Retrospective's maximum duration is three hours This is incorrect. Sprint Retrospective has a timebox duration of four hours For a one-month Sprint, Sprint Retrospective's duration is precisely three hours For a one-month Sprint, Sprint Retrospective's duration can be longer than three hours to get additional valuable feedback from the Scrum Team for future adaptation For a one-week Sprint, Sprint Retrospective's duration is precisely three hours

Give the correct answer: Question 1 As a Product Owner building a Backlog, what pieces of information should you include for each item? Select all that apply. The date the item is due A set value for the item, such as dollar signs A clear description from the perspective of the customer The level of effort required to complete the item Question 2 A Product Owner writing a user story needs the story to fit within the planned Sprint. If the user story is too large, they break it down into multiple scaled-down stories to meet which of the I.N.V.E.S.T. story writing criteria? Independent Negotiable Valuable Small Question 3 As a Product Owner, you need to add estimates to your Backlog for a small number of items. You’d like your team to reach a consensus on the number of items, and you would also like to incorporate the Fibonacci sequence. Which effort estimation technique should you use? Affinity Mapping Planning Poker™ The Bucket System Dot Voting Question 4 Which of the following typically happens during a Sprint? Select all that apply. The Product Backlog is refined by the Product Owner as needed. The project scope is clarified with the Product Owner as more is learned. The work quality improves—or at least stays the same—when compared to the last Sprint. The Sprint Goal is changed by the Product Owner as needed. 5. Question 5 Which of the following is a key deliverable of Sprint Planning? The Sprint Backlog A burndown chart Retrospective notes The project charter Question 6 What typically occurs during the Sprint Review? Select all that apply. Discuss how to better work as a team. Explore which items should be considered done in the Backlog. Demonstrate and inspect the product. Synchronize and prioritize activities for the team. Question 7 Which of the following is a common pitfall in team retrospectives? Allowing team members to mainly focus on the negatives during the review. Allowing team members to ask open-ended questions. Asking team members to take some time to quietly journal reflections. Taking some time to highlight positive moments during the Sprint. Question 8 What’s the overall goal of a burndown chart? Serve as a communication tool for outside stakeholders Provide a way to compare productivity among teams Keep the team aware of how they’re doing against their goals Quantify performance for individual team members Question 9 How would you best compare a Kanban board to a Scrum board? A project team has less use for a kanban board. They’re essentially the same tool with minor differences. The Kanban board is better for tracking Sprint tasks. The Scrum board is more visual. Question 10 Utilizing tools in Scrum helps make the team fully aware of progress and updates. This embodies which Scrum pillar? Transparency Commitment Adaptation Inspection