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.
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.”
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.”
Spike: A spike is a type of user story that is used to research a question or gather information rather than produce a shippable product increment. It helps the team understand the requirements and potential solutions.
Research: By executing a spike, the team can investigate the best practices, tools, and techniques for implementing security firewalls. This research will provide valuable insights and reduce uncertainties.
Informed Decisions: The information gathered from the spike will enable the team to make informed decisions about how to integrate security features into the product backlog and prioritize them effectively.
Collaboration: This approach encourages collaboration between the team and the product owner, ensuring that the security requirements are well understood and addressed.
BMC-Benchmarking is a business practice that will aid in the study, refinement, and application of agility principles. Our certifications demonstrate the corporates, individual level of competence in order to fit any domain that require ITSM benchmarking, Scrum agility, and ISO standards.
Read through discussion, I changed my mind to D (Originally, I though C was best but changed ...)
Starting from action Option-D for clarification of PO's capability and how to support PO.
Then move to the step Option-C as supporting PO, team confirm requirement and gathering information to think about architecture, then sometime take SPIKE as part of Option B.
In the last, whether PO or team member register userstories, this is option A.
If team try to follow Option-A at first, they should know detail requirements and behavior of security feature, this might not be defined on product vision so it shall be difficult.
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.
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).
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).
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
HTTPS
Highly Voted 3 years, 3 months agoHTTPS
3 years, 3 months agoAdmirable
3 years agoHTTPS
3 years, 3 months agoPetrevski
1 year, 4 months agoHTTPS
3 years, 3 months agothewalker
Most Recent 2 weeks, 6 days agoANEE167
1 month agoPuranDom
1 month agofkr
3 months, 3 weeks agoMichaela0015
8 months, 1 week agoNhuho
1 year, 2 months agotThye
1 year, 3 months agoPetrevski
1 year, 4 months agoMinhha3
1 year, 5 months agoInvisibleBeing
1 year, 7 months agoEli8
2 years, 1 month agorichck102
2 years, 2 months agoAdmirable
3 years agoAdmirable
3 years agoAdmirable
3 years, 2 months agoSTW
3 years, 3 months agoSARS
3 years, 7 months ago