29.02.2016 Views

MANAGEMENT

YTntW

YTntW

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5 - REQUIREMENTS ELICITATION<br />

5.1.2 Active Stakeholder Engagement<br />

Stakeholders are a principal source of requirements, which places them at the center of many project and<br />

program issues related to unrealistic expectations, lack of user involvement, and ambiguous, unclear requirements.<br />

For this reason, active support and participation of key stakeholders should be fostered and maintained throughout<br />

the elicitation process. Input should be collected from a broad, diverse set of stakeholders to confirm that varying<br />

perspectives are captured and to reduce the risk of missing requirements.<br />

5.1.3 Defined Business/Organizational Need<br />

A properly conducted needs assessment lays the foundation for achieving the goals and objectives of the<br />

business or organization. A comprehensive understanding of the business need, problem, or opportunity helps to<br />

determine that the right information is elicited and the appropriate stakeholders and elicitation techniques to obtain<br />

that information are selected.<br />

5.1.4 Domain Knowledge<br />

The person responsible for elicitation should be competent in the domain or have access to subject matter<br />

experts for support so as to ask the right questions during elicitation activities. Understanding the relevant terms,<br />

processes, and procedures within a specified domain greatly increases the ability to accurately define and examine<br />

requirements.<br />

5.2 Requirements Elicitation Activities<br />

At this point, eliciting requirements for the solution is performed to address the defined problem/opportunity.<br />

Elicitation involves the discovery and translation of needs into requirements and includes the following activities:<br />

selecting the appropriate elicitation techniques, conducting the actual elicitation, and documenting the outputs.<br />

5.2.1 Plan for Elicitation<br />

Before the actual elicitation, more detailed preparation is required such as drafting agendas, scheduling<br />

conferences for elicitation workshops, inviting stakeholders, etc.<br />

Careful consideration should be given to the following elements:<br />

• Activities. Even though activities were previously defined in Requirements Management Planning, now<br />

that more is known about the problem/opportunity to be solved or addressed and the stakeholders<br />

involved, the techniques to be used are revisited. Generally, a combination of techniques is employed<br />

depending upon the organizational culture, schedule constraints, and relevant knowledge and skills of<br />

the person responsible for eliciting requirements.<br />

26 ©2016 Project Management Institute. Requirements Management: A Practice Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!