Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Separating requirements descriptions from their prioritisation
Previous Previous
 
Next Next
New Post 7/2/2013 9:53 AM
Poll
User is offline neil
1 posts
No Ranking


Separating requirements descriptions from their prioritisation 

A BA where I work instists on writing his requirements in a form where he uses the MoSCoW categorisations keywords within the requirement descriptions.  Hence the requirements all take the form of:

Requirement Priority
The system must do A M
The system should do B S
The system could do C C
The system will not do D W

so for any requirement that he has categorised as M the requirement text will contain the word "must", any that are categorised as C will contain the word "could" etc. 

I have suggested to him that this is poor form.  In my view it renders the priority column redundant.  Re-prioritising the requirements means having to change the requirement description.  Particularly confusingly, any W priority requirements could potentially be read as a double negative.

In it's simplest form, I'd suggest to him rewriting the above as

Requirement Priority
The system shall do A M
The system shall do B S
The system shall do C C
The system shall do D W

Then the steps of writing the requirement and categorising it are not confused, requirements can be reprioritised without needing to edit the requirement description, and the annoying double negative is removed.  However, he insists that his way of doing it is correct.

My question is, is it accepted practice for BAs to write requirements in this style?  Am I being too picky in objecting to this, or am I correct that it is poor form?  And does anyone have a reference to any advice that would back up this argument one way or another?

Thanks.

 

 
New Post 7/2/2013 8:43 PM
User is offline Kimbo
441 posts
5th Level Poster


Re: Separating requirements descriptions from their prioritisation 

Hi Neil,

There is no right or wrong way to right requirements really just good practice. As long as everyone uses the same approach on your project then there is no real issue. So you guys should work out which way you will do it and stick with it.

Now having said that, I agree with your argument and personally use the second version above.

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Separating requirements descriptions from their prioritisation

Community Blog - Latest Posts

Jason White
Jason White
With time, we have evolved from oiled lamps to ever-present electricity, printing every page manually to now producing thousands of copies a day and so on. But what is the one thing these distinct things have in common? Yes, technology.One such branch of technology that has crossed leaps and bounds and turned into a  working technology fr...
1 Responses
Digital Business Analysis
Digital Business Analysis
Nowadays, companies like Audi and HSBC, use IT systems in everything they do. Does that make them to be IT companies rather than banks? Most would probably agree that HSBC is a bank, just as Audi is a car manufacturer. But what about digital banks such as Chime or companies offering digital products? In digital companies, most of the employees work...
1 Responses
Digvijaybook
Digvijaybook
IT companies are rapidly looking or adapting modern methodologies, so the business analyst role is increasing day by day. Offline is shifting to online, and this is why today, companies can easily garner important data in any aspect. But, data itself has no meaning hence, organizations look for a business analyst who can analyze the data and draw a...
3 Responses






Latest Articles

An Introduction on Artificial Intelligence and Machine Learning
Feb 23, 2020
0 Comments
After some research, I was taken back with so many machine learning applications already in use: weather forecasting, medical diagnoses, law enforceme...
Copyright 2006-2020 by Modern Analyst Media LLC