The correct answer is D - Ensure that planning and prioritizing includes consideration of security requirements.
Non-functional requirements (such as security, performance, or compliance) must be included in backlog prioritization and planning sessions. Agile teams must incorporate these concerns into their definition of done and acceptance criteria to ensure continuous compliance and product integrity.
PMI Agile Practice Guide emphasizes:
"Non-functional requirements (NFRs) must be prioritized and planned for alongside functional user stories.
They are not optional, and failure to include them early often leads to system failure or technical debt." (PMI Agile Practice Guide, Section 5.3 - Planning Considerations) Mike Griffiths writes:
"Agile teams should treat NFRs as constraints that are baked into every sprint. Rather than isolating them, they should be considered in backlog refinement and story definition." (PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Other options:
* A may help, but meeting agendas alone are not sufficient for managing NFRs.
* B may assist with knowledge, but it doesn't guarantee prioritization.
* C implies treating the NFR as a risk rather than a core requirement.