Download Latest ECBA Questions

Understanding the scope of elicitation when initially assigned work is crucial for planning the business analysis approach. This involves determining the type of business analysis information to be discovered and selecting the appropriate techniques for elicitation. It requires a clear understanding of the business domain, corporate culture and environment, stakeholder locations, and the dynamics of the stakeholders involved. This foundational step ensures that the business analysis activities are aligned with the project’s needs and objectives. References: The answer is corroborated by the Business Analysis Body of Knowledge (BABOK) Guide, which emphasizes the importance of planning the business analysis approach as part of the scope of elicitation1.

 The task of defining design options involves identifying, exploring, and describing different ways of meeting the business need. This includes defining the solution approach, identifying opportunities to improve the business, allocating requirements across solution components, and representing design options that achieve the desired future state. It is about considering various possibilities that could be created (building), purchased (buying), or a combination of both, to satisfy the business need. References: The information is based on the BABOK® Guide, specifically the section on ‘Define Design Options’ which outlines the purpose and activities involved in this task12.

Poorly managed stakeholder collaboration can lead to detrimental effects on the business analysis process, one of which is resistance to approving elicitation results. When stakeholder relationships are not adequately maintained, stakeholders may lack trust in the business analysis process and its outcomes, leading to reluctance or resistance in confirming and approving the information gathered during elicitation. This resistance can stem from a lack of engagement, poor communication, or misunderstandings about the change's impact, ultimately hindering the progression and success of business analysis activities by impacting the quality of information and stakeholder participation.

In Requirements Life Cycle Management, the task that extends the value of requirements beyond the current initiative is Maintain Requirements. This involves keeping requirements accurate, up to date, and available for reuse in future initiatives. Reusable requirements reduce the need for rework and improve organizational efficiency.

Exact Extract from BABOK® Guide v3 – Section 5.3: Maintain Requirements:

“The purpose of Maintain Requirements is to retain requirements accuracy and consistency throughout and beyond the change during the entire requirements life cycle and to support reuse where appropriate.”