Hello all,
I am creating a requirements document and I have included a weight measurement for the features I am requiring.
Now without getting into the somantics around 'require', I am requesting some opinions on the weighting scale.
I am using a three point scale with a Three being a feature that the prospective product must have or we don't want to look at it. A Two designates a feature that will significantly improve performance if it is included. A One designates a feature that we want the product to have, but not at the expense of a Two or Three feature....
Clear as mud? OK
My objective is to get those designations into a concisely worded, crystal clear scale. Something along the lines of 3 = Must Have feature. The problem is that a 1 isn't a "like to have" feature. It's still a requirement, just lower on the totem pole.
Opinions?
~Thadeus
I am creating a requirements document and I have included a weight measurement for the features I am requiring.
Now without getting into the somantics around 'require', I am requesting some opinions on the weighting scale.
I am using a three point scale with a Three being a feature that the prospective product must have or we don't want to look at it. A Two designates a feature that will significantly improve performance if it is included. A One designates a feature that we want the product to have, but not at the expense of a Two or Three feature....
Clear as mud? OK
My objective is to get those designations into a concisely worded, crystal clear scale. Something along the lines of 3 = Must Have feature. The problem is that a 1 isn't a "like to have" feature. It's still a requirement, just lower on the totem pole.
Opinions?
~Thadeus