4. Done

Sam is the Scrum Master for a Scrum Team. One of the Developers approaches Sam’s and tells her that they are not completing the integration testing for all of the selected Product Backlog Items in the Sprint. Integration testing is part of the agreed definition of "Done". Developers have discussed with the Product Owner and decided to change the definition of "Done". Which two actions should Scrum take?

• Ask the Developers and Product Owner, "Will removing integration testing from the definition of "Done" allow the team to produce potentially valuable increments at the end of every Sprint. If not then, it should not be allowed.

• Make sure that the quality of the increment does not decrease by changing the definition of “Done”. If it does, it should not be allowed

• Disagree with the Developer and tell them that having a stringent definition of "Done" is important for the quality of the product, and they should follow it.

• Agree with altering the definition of "Done" as both the Developers and Product Owner agree.

• Ask the team to wait as the definition of “Done” can only be changed during Sprint Retrospective.

Charles and James are talking about velocity and technical debts. In what two ways is velocity and technical debt related? (Choose the best two answers.)

• Adding higher estimates to technical debt product backlog items will allow the Scrum Team to maintain constant velocity therefore ensuring predictability.

• They are not related because technical debt is non-functional, and velocity is calculated based on end user functionality.

• A Scrum Team can artificially increase velocity by allowing technical debt to be incurred.

• As the Developers are working on new Product Backlog items, they may unexpectedly run into technical debt that will result the team’s velocity dropping.

Your company has notified the stakeholders that they will be having the first release of a new product within ten Sprints. During the seventh Sprint, the Scrum Team discovers that they will not be able to include all of the expected features within the first release. The Product Owner believes if they remove some items from the Definition of Done they will be able to accelerate the development process. Developers objects to this idea as it will lead to technical debt. As a Scrum Master, what would be the best two ways to explain the impact of technical debt? (Choose the best two answers.)

• As long as there is still technical debt in the current release, feature development for the next release cannot be started. The Product Owner must first agree to fixing this before allowing changes to the Definition of Done.

• Releasing the version upon a reduced Definition of Done creates false assumptions about the actual state of the system. This will create many interruptions during the development of the next release as fixes will need to be done to the previous release caused from a reduction of quality.

• The amount of technical debt will need to be analyzed in order to understand the impact on subsequent releases in order to allocate additional Sprints at the end of the project.

• Reducing the Definition of Done will introduce unknown errors as development progresses and functionality is added. The system can become more difficult to stabilize as work progresses. Development for the actual release as well as future releases will be slowed down in unpredictable ways.

A management team member does not understand the value of spending so much time on defining the “Definition of Done”. As a Scrum Master, you can explain that the benefits of “Definition of Done” are: (Choose all that Apply)

• The definition of done helps determine the amount of work completed and amount of work remaining to create a valuable increment by the end of the Sprint.

• The definition of done is a checklist to monitor the Scrum Team members progress towards a task.

• The definition of done creates transparency and provides a common understanding of “done” state of the increment presented at the Sprint Review.

• It helps compare the Scrum Teams efficiency.

A Scrum Team has requested additional time towards the end of the release to integrate with the work produced in the previous sprints increment. They also need time to do additional testing before releasing. (Multiple browser Testing, Multiple DB Testing etc.). What scenarios most likely occurred? (choose the best answers)

• The testing team members must not be working at the velocity expected.

• The team’s definition of done might not be comprehensive enough or incomplete (integration work and testing might not be included)

• This is normal as end to end integration testing can only happen towards the end of the release and will need additional time.

• The Definition of done is being ignored by the Team.

• Scum must have been customized to the teams need

Allowing technical debt to be incurred can allow the Scrum Team to deliver more items in a given period of time. This gives the perception that the Scrum Team has a higher velocity than what it actually has.

• True

• False

By the end of the Sprint, a Product Backlog item in the Sprint Backlog does not meet the team’s definition of "Done". What two things should happen with the item?

• Extend the Sprint, to give you enough time to complete the item.

• Include it in the Increment to be inspected at the Sprint Review. Partly completed items can be reviewed at the Sprint Review.

• Do not include the unfinished item in the Increment. Do not show the item in the Sprint Review.

• Estimate the amount of work remaining to make it ‘Done’ and add it to the Product Backlog for the Product Owner to decide what to do with it.