Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Requirement Context Question
Previous Previous
 
Next Next
New Post 4/15/2011 9:31 AM
User is offline Irene
31 posts
9th Level Poster


Requirement Context Question 

I’ve seen requirements starting with “Ability to …”, and have a separate column of priority as High, Medium or Low depending on its importance.

I’ve also seen people using “Must be able to …”, “Should be able to…” in business requirements. I am not sure if I understand MoSCoW analysis, is this the way of how to use MoSCoW?
 
Which method do you think better describes requirements? If using the second one, do you think it is still necessary to have “Priority” column?
 
Thanks very much for your inputs!
 
Irene
 
New Post 4/17/2011 2:52 AM
User is offline Kimbo
456 posts
5th Level Poster


Re: Requirement Context Question 

 Hi Irene,

I think its important to separate the priority from the actual requirement. Two different things entirely. Putting them together is lazy and will make any kind of automation difficult. For example, estimating with multipliers based on the priority. If the priority is hidden in the requirement text, how do you estimate accurately (is that a contradiction in terms?)

Kimbo

 
New Post 4/17/2011 5:31 PM
User is offline KJ
243 posts
6th Level Poster


Re: Requirement Context Question 

Irene,

I prefer the former. Define declarative requirements in the usual, "the system shall ... " phrases, then do the MoSCoW.

warm regards,

K

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Requirement Context Question

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC