I will always shout it from the rooftops that requirements are the lifeblood of the project. And accurate, complete, and detailed definition and documentation of project requirements is absolutely essential in order to ensure that the delivery team is creating the right, usable end solution for the project client.
On to the next concept. Are all requirements created equal? No. Some are ‘absolutes’, some are ‘needed’, and some are the ‘nice-to-haves.’ I like to refer to these as 1’s, 2’s, and 3’s in terms of prioritization of requirements. Why prioritize? Because inevitably some requirements are or have been scoped into the project that may either end up not being feasible or may end up not being wanted or needed. And cost can always enter into that factor as well. Either in terms of keeping the cost down from the start or in terms of getting the project financials back on track when unforeseen work or a large change order has pushed the project over budget.
On to the next concept. Are all requirements created equal? No. Some are ‘absolutes’, some are ‘needed’, and some are the ‘nice-to-haves.’ I like to refer to these as 1’s, 2’s, and 3’s in terms of prioritization of requirements. Why prioritize? Because inevitably some requirements are or have been scoped into the project that may either end up not being feasible or may end up not being wanted or needed. And cost can always enter into that factor as well. Either in terms of keeping the cost down from the start or in terms of getting the project financials back on track when unforeseen work or a large change order has pushed the project over budget.
RSS Feed