Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Planning for requirements gathering and elicitation
Previous Previous
 
Next Next
New Post 1/21/2013 6:04 PM
User is offline Perry McLeod
70 posts
8th Level Poster




Re: Planning for requirements gathering and elicitation 

 Try using the following RAM:

  • R = Responsible
  • A = Accountable
  • S = Support
  • C = Consulted
  • I = Informed
  • O = Observing

It's the last one "O" that I draw your attention to.  In your meeting agenda you assign "O" to the developers and designers.  They are invied to the workshop but as observers only.  This keeps them in the loop while freeing up the meeding for a true needs assessment.  This must be socialized with the stakeholders, the team, the PM and the sponsor.

Perry

 
New Post 1/29/2013 1:43 AM
User is offline sp_key
7 posts
10th Level Poster


Re: Planning for requirements gathering and elicitation 

 Guys,

Many thanks for your valuable input.

I had to delay my response as I took a few days to read more about what you have recommended.

I think the Context diagram is a very good advice which I will try to implement. Not sure about DFDs though as it seems too complicated for what we're doing which is mobile apps. 90% of them do not even have a back end. Activity diagrams should, in my opinion, be sufficient

 
New Post 2/1/2013 11:12 AM
User is offline Anthony Chen
63 posts
8th Level Poster


Re: Planning for requirements gathering and elicitation 
Modified By Chris Adams  on 2/1/2013 2:19:20 PM)

 We have a list of models for RML that is pretty comprehensive from a requirements point of view. We organize the models into people, systems and data models. People models organize information from a user point of view. System models organize information about the ecosystem and individual systems. Data models organize the flow of data through the system and individual data elements (from a business not technical point of view).

http://www.seilevel.com/wp-content/uploads/RML-Language-for-Modeling-Software-Requirements1.pdf

 

Here are some articles on how to prep sessions. If you search the seilevel blog you will probably find more.

http://requirements.seilevel.com/blog/2008/07/how-to-prepare-for-requirements-sessions-with-your-users-tip-1.html

http://requirements.seilevel.com/blog/2006/04/jad-sessions-part-1-the-need.html

http://preview2.seilevel.com/2006/04/jad-sessions-part-2-roles/

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Planning for requirements gathering and elicitation

Community Blog - Latest Posts

So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...
Elicitation involves bringing out or drawing out information. Elicitation is a key task in business analysis as without proper elicitation the requirements for the solution to the business needs cannot be identified. 1. Not understanding underlying business need Organization’s business environment keeps changing with respect to Customer...
TOGAF is a certification that is handed over by The Open Group. It is an open corporate architecture means used to improvise upon the business effectiveness across the world’s leading business set-ups. Aspirants wishing for a successful career in corporate architecture must go for the TOGAF certification in order to explain the...

 



 

Copyright 2006-2021 by Modern Analyst Media LLC