Is there an agreed upon PMBOK (or other) set order to evaluate a requirement's properties to get an estimate of what it will cost?
e.g. if you're creating a project estimate (any methodology, framework or stage of the project), when your review requirement(s), do you evaluate its resourcing impact first, then it's timeframe second, then its complexity third (and so on) in a set order?
My view that there is not.
Summarize the problem
I am a business analyst being asked to describe the properties of a body of project requirements that affect project estimates and the set order in which these properties are assessed in. For example, requirements for a payment gateway with a high number of interfaces could be expensive (this task could be given to many developers and involve 3rd parties, so high complexity is expected), whereas a contact form on a website should be simple (this task could be given to any developer, so low resourcing issues are expected) and inexpensive. Do we assess a requirement's complexity first or it's resourcing impact first?
Properties of the requirements I have put forward are
- Number of requirements - the greater number, the more expensive (in general)
- Complexity of requirements the more complex, the more expensive (in general)
- Skill mix - the more specialised, the more expensive (in general)
- Internal resourcing - the more need for using up BAU resources, consultants and partnering, the more expensive (in general)
- Priority of requirements - the more Must haves, the more expensive (in general)
- Time frame - the more urgent, the more expensive (always!)
- Specialised project requirements - the more obscure, the more expensive (in general)
and so on
Provide details and any research
- I have asked other Project managers internal to our organisation
- I have asked friends
- Googled phrases similar to "in what order do we assess a requirement property to provide project estimates?"