nerdexam
IIBA

CBAP · Question #436

A national branch of a global company is struggling to improve business processes of its Public and Government Affairs (PGA) department. To work with external stakeholders effectively, PGA employees…

The correct answer is B. Utilize the solution in a test environment with actual data to elicit feedback. When users resist a system due to poor usability, having them interact with a prototype or test environment using real data is the most effective elicitation technique to surface concrete, actionable feedback.

Elicitation and Collaboration

Question

A national branch of a global company is struggling to improve business processes of its Public and Government Affairs (PGA) department. To work with external stakeholders effectively, PGA employees need to collect, manage, and exchange a vast amount of information. Complex cases involve collaboration of many employees from different departments. The ability to share information and to coordinate corresponding activities is crucial for the company's growth plans. Their current tools and practices do not serve the purpose well. The existing system, which was deployed a couple of years ago, has only a few active users. The majority of PGA employees avoid using it because the system is hard to use and lacks needed functionality. Consequently, available information is mostly unstructured and stored either locally or on a shared network drive. Some of the information exists only in a paper form. The branch's PGA head, who sponsors the project, wants to implement a configurable solution that two other branches successfully deployed several months ago. Both deployments were done by three solution consultants, who will be available to assist in the project. They will be responsible for tailoring the solution to PGA needs, as well as for training the PGA staff. With their help, the sponsor plans to complete the project in approximately three months. The solution consultants reside in another country 7 hours ahead of the rest of the project team. They will be available part-time, but are planning two one-week long trips to the PGA central office to conduct initial training and to participate in the final deployment of the system into production. The consultants, in turn, expect a business analyst (BA) to assist in collecting necessary data and defining customization requirements. A BA suggests interviewing employees to elicit user requirements and then performing a gap analysis to identify solution customization requirements. However, the sponsor believes that it will be a waste of time because the employees do not know how the process should work in the future. The sponsor expects the solution to help shape their process and wants to start with the solution as is, amending it as necessary based on the user feedback. What should the BA do?

Options

  • ADeploy the current solution and survey users for improvement proposals.
  • BUtilize the solution in a test environment with actual data to elicit feedback.
  • CCollect the requirements from the sponsor and domain subject matter experts.
  • DExplain the benefits of interviews to the requirements elicitation process.

How the community answered

(26 responses)
  • A
    4% (1)
  • B
    81% (21)
  • C
    12% (3)
  • D
    4% (1)

Why each option

When users resist a system due to poor usability, having them interact with a prototype or test environment using real data is the most effective elicitation technique to surface concrete, actionable feedback.

ADeploy the current solution and survey users for improvement proposals.

Deploying the current failing solution to production before gathering proper requirements repeats the same mistake and exposes active operations to a known inadequate system.

BUtilize the solution in a test environment with actual data to elicit feedback.Correct

Using the solution in a test environment with actual data is a prototyping and observation-based elicitation technique that overcomes user disengagement by making feedback tangible and specific. Real data triggers authentic user reactions, surfacing usability issues and missing functionality that abstract interviews or surveys often miss. This approach is especially effective when the user population is already skeptical of the system.

CCollect the requirements from the sponsor and domain subject matter experts.

Collecting requirements only from the sponsor and subject matter experts excludes the majority of end users whose day-to-day friction is the root cause of low adoption.

DExplain the benefits of interviews to the requirements elicitation process.

Explaining interview benefits does not constitute elicitation activity and adds no value without actually conducting the interviews or another hands-on technique.

Concept tested: Prototype-based elicitation for low-adoption systems

Source: https://www.iiba.org/standards-and-resources/babok/

Topics

#prototyping#elicitation techniques#feedback collection#user acceptance

Community Discussion

No community discussion yet for this question.

Full CBAP Practice