The product owner wants to build security firewalls into the product.
How can the team members support this?
The product owner wants to build security firewalls into the product.
How can the team members support this?
To support building security firewalls into the product, team members should first seek to understand the product owner's specific security requirements. This involves asking pertinent questions to determine the desired level of security. Once the team has a clear understanding of these requirements, they can more effectively prioritize and plan the necessary actions, including adding detailed items to the backlog or executing research as required.
D - Correct - this is the only option that fosters collaboration and sets the stage for further decomposition. From PMI’s Agile Practice Guide, Page 58: “Bring the team and product owner together to clarify the expectations and value of a requirement. Progressively decompose roadmap into backlog of smaller, concrete requirements.”
A - Incorrect - because you are assuming the role of a team member and only the Product Owner can add items to the product backlog according to The Scrum Guide.
Anyone can add to the product backlog but it is the product owner who prioritizes what the team works on.
B - Incorrect - The team didn’t state nor do they fully understand the requirement to state that they lack the technical or functional skills to develop the security features. Further inquiry into the requirement is necessary before committing to spike. From PMI’s Agile Practice Guide, Page 56: “Spikes are helpful when the team needs to learn some critical technical or functional element.”
Security is a very critical element.
C - Incorrect - because this is answered in the project charter. From PMI’s Agile Practice Guide, Page 49: “Every project needs a project charter so the project team knows why this project matters, where the team is headed and what the project objective is.”
In my opinion, B is the correct answer. Here is why: A = wrong. Indeed, it is true but after C, D, and B. The team cannot prioritize and estimate "built od security firewalls", but can create a spike story, which is a user story that needs more information so the team can estimate how long the story will take to complete. B = correct. It is the very first step, then comes the business analysis (C and D), and concretizing the story (A).
i choose A. We can define the detail later
I go for (D) Agile principle 7: Working software is the primary measure of progress.
D is correct
D. Ask questions to determine if the product owner can define the desired level of security It's crucial to understand the product owner's expectations and requirements regarding security. Asking questions about the desired level of security helps the team gain clarity on the specific security features, functionalities, or measures the product owner envisions. It ensures that the team has a clear understanding of the security goals before adding new features to the backlog or conducting research.
Should communicate with Product Owner further of the requirement. isn't it?
Vote A
A is correct. Read "Admirable's" response in the comments for explanation.
D ????
From the team's perspective, the Answer is D. From the POs perspective the Answer is A.
After much thought and consideration A is the best answer. For the team to work on any user stories, they must first be placed in the backlog. When it is prioritized by the PO this is when the clarification of the requirements will be done as well. The team will ask questions at this point to determine the level of security required as they will need to determine the tasks (breaking user stories down to tasks).
For the team members to support the security requirement, the PO must place in the Product Backlog. A is the best answer.
The 'team' includes the Product Owner, who can add items to the backlog, then it can be estimated with the help of the 'development team' an reprioritized . A is a possible answer.
Spike are for experimental things that aren't well known, not for adding additional requirements.
Answer is A
Why not B? the team should spike it first before deciding to add it into PL?!
Each time we have something new it should not be handled as a spike.
Can'y be A team members don't update backlog.
The Answer is for sure A Remember the PO is the one responsible for adding and prioritize the Product Backlog. Nothing goes direct to the Dev team without it being added to the Product Backlog and prioritized
For sure not A, PO responsible for PB where Development team responsible for IB.