Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  CBAP - Certifie...  Elicitation Question
Previous Previous
 
Next Next
New Post 9/11/2015 10:38 PM
Resolved
User is offline Niraj
1 posts
No Ranking


Elicitation Question 

Can someone please help to answer this question

Cecilia needs to define the business rules, entities and attributes of a desired solution. All subject matter experts are currently tied up in other projects and cannot leave their current responsibilities. She has been given a two month's timeframe to define the desired solution. The best technique Cecilia can use in this situation is:

a. Observation
 
b. Document analysis
 
c. Prototyping
 
d. Surveys

 
New Post 9/26/2015 5:56 PM
Accepted Answer 
User is offline NitWitNick
259 posts
5th Level Poster


Re: Elicitation Question 

For something quick all you say you need to do is define the problem ... I find out what problem they are having, a quick description then go to that department and work with the users.

I'd sit with some people, watch their work flow and have them comment as they were doing something ... what they don't like and what they wished would happen.

So, Observation and questions, comments would be my first choice for actually seeing the problem and taking notes.

I'd find out what they want fixed or created and write requirements and functional stuff (UI / UX,  etc.... talk to your technical people for technical specs.

Draw up some prototype to show the users and ask for approval or changes.

Work with development teams.

 

 

 

 
New Post 10/10/2015 9:09 PM
User is offline Sam
1 posts
No Ranking


Re: Elicitation Question 

The Answer is B.

SME's are busy, so that eliminates a, c and d. Going over enterprise documents to define business rules etc.. can be done without bothering SME's. 

 
New Post 10/12/2015 10:55 AM
User is offline Adrian M.
755 posts
3rd Level Poster




Re: Elicitation Question 

I would say A & B but if only one option is needed, I would go with B.  This is because the question does not state what type of documentation exists (if any).  You can observe users do work and conduct their business without requiring their attention.  

You will be able to identify the 'types of things' they deal with (aka business entities) such as customers, accounts, widgets, orders, complaints.  

You will surely also come across functionally significant attributes (customer.name, order.status, widget.model number, acccount.number) just but listening to your users go about their business.  

You will even hear many business rules (ex: We cannot approve a new account until you we have a copy of your photo id.)  Observation is a good place to start but relying on observation alone to infer business rules will most likely lead to a disaster. 

At one point in the project, the customer will be forced provide feedback.  If they don't make the time during product design then they will, unfortunately and eventually, provide their feedback when they start using the system and it doesn't work they way the expected.

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 11/11/2015 5:22 PM
User is offline Kimbo
454 posts
5th Level Poster


Re: Elicitation Question 

I think there is an option you omitted:

 

e. get another job

Not sure how you're expected to define requirements when the stakeholders aren't making themselves available. You're being set up to fail. beware

 

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  CBAP - Certifie...  Elicitation Question

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC