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 8: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 7:43 PM
User is offline Kimbo
454 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

Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Architecture and AI In our recent conversation with Joseph Edward, we explored the transformative power of business architecture (BA) and technology as tools for uplifting communities. Joseph, with his rich background spanning from education to IT leadership, shared...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - The AI Business Analyst I recently had an engaging discussion with Maria Becerra, a passionate advocate for AI and an accomplished business analyst, on the AI Business Analyst. Maria is a respected name in strategy, business analysis and AI. Her path from Colombia to Canada ...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Analysis. I'm happy to share insights from my recent conversation with Kingsley T. Ihejirika, PhD, an ICT Business Analyst at the Ministry of Justice in New Zealand. Kingsley's unique blend of academic theory and practical expertise sheds light on the path t...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC