I’ve seen requirements starting with “Ability to …”, and have a separate column of priority as High, Medium or Low depending on its importance.
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
Irene,
I prefer the former. Define declarative requirements in the usual, "the system shall ... " phrases, then do the MoSCoW.
warm regards,
K
brought to you by enabling practitioners & organizations to achieve their goals using: