In this five-part series, I will be providing guidance on how to write an effective User Requirement Specification. I will try and pull ideas and information from a number of different sources. For example, I have recently asked people through LinkedIn to provide examples. I would like people to comment on the blog post with their own ideas and own suggestions so that it is a collaborative effort and a living blog.
To start the process off I would like to suggest that people who are writing User Requirements Specifications consider the following points:
Remember the aim of a URS is to specify ‘what’ without going into ‘why’ and an ambiguous URS is worse than an incomplete URS.
Stay tuned for part 2 and good luck with writing your own URS documents. Please feel free to comment on this blog post with your own experiences and suggestions.
From Jim: You can connect and interact with other project execution professionals in the Plan & Design and Implement & Build groups in the Emerson Exchange 365 community.
The post Considerations for Your User Requirement Specification appeared first on the Emerson Automation Experts blog.