Several customers have reported security issues of many features of an existing Product.
What two things can the Scrum Team of this Product do next?
A . Create testing Product Backlog items with testing steps to test other features.
B. Create special test documentation.
C. Adapt the Definition of Done to include security expectations.
D. Add identified changes to the Product Backlog and discuss security expectations of each Product Backlog item.
E. Involve the Customers to test the security before releasing the Product.
Answer: C,D
Explanation:
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. It’s not mandatory to wait for the Sprint Retrospective to change the Definition of Done. It can be done at any time. The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work. When creating and communicating Product Backlog items, the team can discuss security and other non-functional requirements related to each feature.
Latest PAL-I Dumps Valid Version with 305 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund