5.4k views
3 votes
Which is NOT a basic element of Plan when you do repuiremenls elicitation on your project?

A. Expected products of of efforts
B. Keep everyone engaged
C. Elicitation objectives
D. Schedule and resource estimates
E. Elicitation risks
F. Elicitation strategy and planned techniques

1 Answer

6 votes

Final answer:

The element not considered a basic part of a requirements elicitation plan is 'B. Keep everyone engaged', which refers to maintaining buy-in and is not a static component of a project plan.

Step-by-step explanation:

The element that is NOT a basic element of a plan when you do requirements elicitation on your project is B. Keep everyone engaged. This is more of a strategy for maintaining buy-in throughout the project rather than a tangible part of the planning process. A solid elicitation plan would generally include A. Expected products of efforts, C. Elicitation objectives, D. Schedule and resource estimates, E. Elicitation risks, and F. Elicitation strategy and planned techniques. Keeping people engaged is critical, but it is an ongoing process, not a static component of a project plan. It entails securing the engagement and commitment of various stakeholders, such as researchers, community stakeholders, and survivors, and ensuring that they understand the project plan and have opportunities to provide feedback on the project design, survey, and other elements.

User Alex Curran
by
8.8k points