Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  My Approach to requirement gathering in a fast paced project
Previous Previous
 
Next Next
New Post 12/10/2012 6:37 AM
Unresolved
User is offline Nitin
8 posts
10th Level Poster


My Approach to requirement gathering in a fast paced project 

 Dear All,

Currently I  am working on business analysis of CRM. For successful implementation in this very fast paced environment I am following below mentioned approach:

1)    After first meeting with stakeholder I develop a prototype which highlights application flow. This basically shows  what happens on screen when user performs a particular function.

Benefits: Initiates users thought process, you may get detailed picture of application.

2)    Once a prototype for a module is finalized then I start working on use cases for that module.

Benefits: covers all the cases of a particular functionality. It is reviewed by coder so that he can understand the document well.

3)    And once use case document gets over I start working on prototype document where it clearly defines how system will behave for a particular screen. This document is developed with a technical lead.

Benefits: All integrations level aspect start coming into picture in this document. Plus what values need to be captured.

Please share your feedback on same approach. Negative views are more welcomed J

 
New Post 12/10/2012 11:49 AM
User is offline dldelancey
61 posts
8th Level Poster


Re: My Approach to requirement gathering in a fast paced project 

Hmm, I'm wondering if there is a tester or QA specialist of some sort who ought to be included?  To determine if you're covering the details they will need for testing the completed product.  Otherwise, if the stakeholders have been identified properly and they are okay with the approach, and the developers are okay with this approach, then it doesn't matter what the rest of us think.

 
New Post 12/11/2012 9:49 PM
User is offline Kimbo
454 posts
5th Level Poster


Re: My Approach to requirement gathering in a fast paced project 

Nitin,

Sounds like you jump straight into screen detail without working out what the actual business requirements are. Therein lies potential disaster. You're quite likely to deliver stuff that your business users don't want. 

Pull yourself up out of the detail and work out your requirements first. Once you have that worked out, then get into the solution.

Kimbo

 
New Post 12/19/2012 7:54 AM
User is offline Phil
1 posts
No Ranking


Re: My Approach to requirement gathering in a fast paced project 

I've got to agree with Kimbo - You need to at least get your high level requirements established first, what are the business trying to achieve, why etc.  I would also suggest, that you create the use cases at the same time as the prototype - even it's a wireframe, as the use case scenarios should help with the path through the system (alt paths etc).

 
New Post 12/20/2012 11:41 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: My Approach to requirement gathering in a fast paced project 

Nitin:

On the real plus side, you are focused on getting things done, not on creating needless documentation.  But remember, Agile is about creating minimal but quaility (i.e., essential) documentatioin.   As Kimbo mentioned,  it appears that you are largely skipping requirements analysis and  jumping into design.    The one analysis artifact you mention is use cases.   But use cases by them selves lack an integration mechanism.    

If your app is small enough, I guess you can makeif work.  But if you have a larger scale app, you need to scope things out (Context Diagram), and concentrate on the fact that it is not so much the stand alone requirements that need to be discovered, but the essential  interrelationships between them (ie. the data flows).  Do you hav a  need for modeling data requirements?

Your approach:  Screen shots and Use Cases are all that is really needed.  My approach:  Some essential data flow diagrams, entity relationship diagrams, and screen shots is all that is really needed.   

Tony

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  My Approach to requirement gathering in a fast paced project

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