This is the third part of the five part series on how to write an effective User Requirement Specification. The topic of this part is ‘Scope’. If you missed the earlier two, see Considerations for Your User Requirement Specification and Process Overview for Your User Requirement Specification.
The remaining parts will be Control Philosophy and Hardware. As before, I would very much appreciate comments and input into this.
The points which I would like authors of User Requirement Specifications (URS) to consider are as follows:
Remember the clearer you are on scope, the fewer change requests you can expect to see later in the project. If there are items of scope which are unclear, state it in your URS. The proposal could include an indicative price to help with your budgeting if needed then. Even if it is not finalised at the point of quotation and tender vetting, it can still be included in the scope of work later through variation orders.
Please feel free to let me know your thoughts on the scoping of projects in the comments section below.
From Jim: You can also connect and interact with other project professionals in the Plan & Design group in the Emerson Exchange 365 community.
The post Scoping Your User Requirement Specification appeared first on the Emerson Process Experts blog.