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

There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC