Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Difference when Documenting Requirements and Resources
Previous Previous
 
Next Next
New Post 3/28/2019 4:42 AM
User is offline MadiMo
16 posts
9th Level Poster


Difference when Documenting Requirements and Resources 

Hello,

I hope all is well.

I have a simple question, I understand that a Resource is a Requirement in some cases, but many people would rather write resources in separate fields/documents, When you write the requirements how do you differentiate between a resource and a requirement? It seems confusing to me 

 

I appreciate your advice

 

 

 

 

 
New Post 7/17/2019 12:25 AM
User is offline Stewart F
96 posts
7th Level Poster


Re: Difference when Documenting Requirements and Resources 

 

Hi MadiMo, 

I think this is a perfectly understandable question. Some companies will include things such as resources in their requirements and others will go a slightly different route, by adding it in a Business Case for example.

Neither are right or wrong. It just depends on what the company you work for does. 

So, lets answer your question. 

If we assume that a resource is a person or a thing (such as a specialist piece of equipment) then saying that you need one (or more) in order to do the job, could be construed as a non-functional requirement. You aren't asking it to actually do anything, you are just saying that to meet expected capacity you need x number of people (if we use the people resource example). 

So if I were to add them into my requirements, it would be as a non-functional requirement.

If it is a piece of equipment, the same is still true. You haven't said in you requirement that it should 'Open an envelope' for example. So it still counts as a non-functional requirement. 

The difficulty with this though, is that it is often easy for everyone to forget about this type of requirement. So, I would also make sure that the Project Manager, Sponsor and Product Owner (if you have any of those) are aware of this early on, and remind them of the requirement periodically. As the BA, you may be challenged later on to prove that this requirement was met - that wont be easy unless you can actually point to the new person, or piece of equipment. 

I know your original question was around 4 months ago, but if you do read this, I would be interested to know what the Resource was in this case. Just me being nosey !!

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Difference when Documenting Requirements and Resources

Community Blog - Latest Posts

Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses
Jason White
Jason White
New technology is in trend every day and striving to make its mark to be the best. It is not optional to stay exceptional, technology has made lives easy and uncluttered in so many ways that cannot be comprehended. With the latest technologies in the headlines every day, it is Artificial intelligence that is leading the race and being incorporated ...
0 Responses
Digvijaybook
Digvijaybook
The role of a business analyst is to manufacture a piece of art; the piece of art varies depending upon the methodology and techniques being used. Business analyst serves the project all through the beginning until the end and comes up with different pieces of art. It all depends on the case, the business analyst gets involved from the beginning of...
0 Responses






Latest Articles

Requirements Life Cycle Management with Azure DevOps
Jul 05, 2020
0 Comments
Requirements management is a critical function for business analysis. Requirements management is focused on ensuring that the business users and stake...
Copyright 2006-2020 by Modern Analyst Media LLC