What should a Development Team do with non-functional requirements?
Correct Answer:
A
Non-functional requirements should be worked on alongside functional development.
Steven is a Scrum Master asked to assist in creating five new Scrum Teams that will be working to build a highly anticipated product. He talks with them about the importance of being able to integrate their Increments by the end of their Sprints. This includes the first Sprints. The product is very important to both the end users and the organization.
Of the choices raised by future team members, what would Steven encourage?
Correct Answer:
C
When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of “Done” to have a shared understanding of what it means for work to be complete, to ensure transparency. Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.
A Scrum Team has requested a hardening Sprint to integrate the work produced in previous Sprints and test before releasing.
What three scenarios has likely occurred? (Choose three.)
Correct Answer:
ABC
At the end of a Sprint, the new Increment must be ‘Done’, which means it must be in useable condition and meet the Scrum Team’s Definition of Done.
During the Sprint, the Development Team realizes they might not be able to finish all of the items in the Sprint Backlog.
What should happen?
Correct Answer:
C
Which stakeholder is the most important for the Product Owner to satisfy?
Correct Answer:
D
The highest priority is to satisfy the end users.