What should the Development Team do if they are approached by someone outside the team and asked to add a “very important” item to a Sprint that is in progress?

1. A. Add the item to the bottom of the Sprint Backlog.
2. B. Replace an item in the current Sprint of equal size.
3. C. Add the item to the top of the next Sprint Backlog.
4. D. Inform the Product Owner so he/she can work with the person.

Correct Answer: D
Allow the Product Owner to decide what to do with the item as he/she is responsible for the flow of value.

Which of the following is true about the Product Owner role?

1. A. Can be shared between multiple people on a Scrum Team, Is the same as a Project Manage
2. B. Is played by a committee or a team of people.
3. C. Is one perso
4. D. Can be influenced by a committe
5. E. Is accountable for ordering the Product Backlog.

Correct Answer: B

During Sprint Planning, the Definition of Done will help the Development Team forecast the amount of work, selected from the Product Backlog, deemed feasible to make ‘done’ by the end of the Sprint.
Which two items best describes what ‘done’ means? (Choose two.)

1. A. All the work needed to prepare the Increment for User Acceptance Testing.
2. B. All the work needed to prepare the Increment for Integration Testing.
3. C. Having an Increment of working software that is potentially releasable to the end users.
4. D. All the work performed as defined in the Definition of Done.
5. E. All the work completed within the current skills and expertise in the Development Team.

Correct Answer: CD
When a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means. Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the Definition of Done for the Scrum Team and is used to assess when work is complete on the product Increment. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current Definition of Done.

Technical Debt can lead to false assumptions about the current state of the system and the Increment reviewed
at the end of the Sprint.

1. A. True
2. B. False

Correct Answer: A
Technical debt is any shortcomings in the code. It is a natural by-product of software development (unavoidable) and can at best be managed. If neglected, it will compound and have a negative effect on the team’s ability to the deliver value. A team can have an artificially high velocity by taking shortcuts or introducing technical, debt into the system. This can give a false assumption about the current state of the product. It can look good on the surface but underneath can be a mess.

Which approach would you recommend to ensure that the Product Backlog items discussed at Sprint Planning are well understood, actionable, and easier to forecast?

1. A. Having a separate group of business analysts and functional testers analyzing high-ordered Product Backlog items before Sprint Planning.
2. B. Having the Product Owner work with stakeholders between the end of the last Sprint and before beginning the next to prepare the Product Backlog items so not to interrupt the Development Team.
3. C. Having the business analysts in the Development Team create the upcoming Product Backlog items during a Sprint and adding them to the next Sprint’s forecast.
4. D. Having the Development Team use some time during each Sprint to help the Product Owner analyze, estimate, and design items at the top of the Product Backlog that is projected to be worked on in the upcoming Sprint.

Correct Answer: D
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.