Home

	Submit Your Article
	Member Login
	Top Authors
	Recently Added Articles
	Most Popular Articles
	Submission Guidelines
	Categories
	RSS Feeds

For Everyone »

	Sitemap
	Add to Favorites
	Top Article Directories
	Top Web Directories

Directory »

	Link to us
	Directory

Ten Top Tips for Creating Good Business Requirements

© By: Niall Kennedy

Creating good business requirements will go a long way towards ensuring the success of the project and eliminate design and development risks that result from poor business requirements documentation...

Return to Article

You have permission to publish this article electronically or in print, free of charge, as long as you leave the article title, author name, body and resource box in tact (means No changes) with the links made active and you agree to our posted publisher terms of service.

Use the tools below to copy the article in plain text form, or you can copy it as HTML, ready to copy and paste directly into a web page.

Word Count Appx. : 473
Total Views : 112

HTML Version	<h1>Ten Top Tips for Creating Good Business Requirements</h1> © By: <a href='http://fileblogs.com/index.php?page=author&author_name=Niall+Kennedy' target='_blank'>Niall Kennedy</a><br><br> <br> <p>Creating good business requirements will go a long way towards ensuring the success of the project and eliminate design and development risks that result from poor business requirements documentation. Here are the Top 10 Tips for Writing Good Business Requirements:</p> <p>1. Develop a clear understanding of the problems that the proposed software is being designed to solve. This will ensure that the subsequent business requirements document addresses those problems fully.</p> <p>2. Identify all project stakeholders and involve them in the business requirements gathering process from the start. Work to build trust and establish credibility early on so you can maintain stakeholder support throughout the project. Learn the individual personality traits of each stakeholder in order to be able to better manage them during the requirements phase of the project.</p> <p>3. Clearly document all business data including workflow, current problems, anticipated risks, and required performance metrics. Use project-approved tools and methodologies to ensure that the documentation conforms to the client’s requirements.</p> <p>4. Use approved templates for all documentation. Ensure that terms used throughout all documentation either exist in the project dictionary or are added as required. No one reading the business requirements document should encounter unfamiliar terms that cannot be quickly resolved by reviewing the project dictionary.</p> <p>5. Identify potential privacy and security issues early on so these problems can be mitigated to a level which satisfies the stakeholders that these risks have been managed properly. This helps to build trust and ensures that stakeholders remain committed to the project.</p> <p>6. Make a concerted effort to identify and document all risks, the impact of these risks on the project’s costs and timetable. This will avoid unexpected project delays as well as help control runaway costs.</p> <p>7. Conduct both group and one-on-one meetings to insure that all business requirements, risks and concerns are identified.</p> <p>8. Present a draft of the business requirements document to key stakeholders for preliminary review and tentative approval. This helps to ensure that the final business requirements document will be more easily accepted by all stakeholders when it is presented.</p> <p>9. Rewrite the draft business requirements document to address any issues discovered during step #8. This may requires repeating the stakeholder meeting process until you are sure that all issues have been identified and documented.</p> <p>10. Present the completed business requirements document to all stakeholders in a formal meeting. Take notes in order to maintain the collective project memory and be ready to address any issues or concerns which may be raised.</p> <br> <p>Niall Kennedy is an internet marketing consultant. Positive is a UK provider of professional <a target="_new" href="http://be-positive.co.uk/code/ourwork-gold.html">Business Analysis</a>. Contact Positive at <a target="_new" href="http://www.Be-Positive.co.uk">http://www.Be-Positive.co.uk</a> for more information about <a target="_new" href="http://www.be-positive.co.uk">Requirements Documentation</a>.</p> <p>All rights reserved. This article may be reprinted in full so long as the resource box and the live links are included intact. Copyright Be-Positive.co.uk</p> <p>All rights reserved. This article may be reprinted in full so long as the resource box and the live links are included intact. Copyright Be-Positive.co.uk</p> <br><br> Read more Articles on <a href='http://fileblogs.com/Top7-or-10-Tips&category_235' target='_blank'>Top7 or 10 Tips</a> at <a href='http://fileblogs.com' target='_blank'>FileBlogs.com</a>
Plain Text Version	Ten Top Tips for Creating Good Business Requirements © By: Niall Kennedy Creating good business requirements will go a long way towards ensuring the success of the project and eliminate design and development risks that result from poor business requirements documentation. Here are the Top 10 Tips for Writing Good Business Requirements: 1. Develop a clear understanding of the problems that the proposed software is being designed to solve. This will ensure that the subsequent business requirements document addresses those problems fully. 2. Identify all project stakeholders and involve them in the business requirements gathering process from the start. Work to build trust and establish credibility early on so you can maintain stakeholder support throughout the project. Learn the individual personality traits of each stakeholder in order to be able to better manage them during the requirements phase of the project. 3. Clearly document all business data including workflow, current problems, anticipated risks, and required performance metrics. Use project-approved tools and methodologies to ensure that the documentation conforms to the client’s requirements. 4. Use approved templates for all documentation. Ensure that terms used throughout all documentation either exist in the project dictionary or are added as required. No one reading the business requirements document should encounter unfamiliar terms that cannot be quickly resolved by reviewing the project dictionary. 5. Identify potential privacy and security issues early on so these problems can be mitigated to a level which satisfies the stakeholders that these risks have been managed properly. This helps to build trust and ensures that stakeholders remain committed to the project. 6. Make a concerted effort to identify and document all risks, the impact of these risks on the project’s costs and timetable. This will avoid unexpected project delays as well as help control runaway costs. 7. Conduct both group and one-on-one meetings to insure that all business requirements, risks and concerns are identified. 8. Present a draft of the business requirements document to key stakeholders for preliminary review and tentative approval. This helps to ensure that the final business requirements document will be more easily accepted by all stakeholders when it is presented. 9. Rewrite the draft business requirements document to address any issues discovered during step #8. This may requires repeating the stakeholder meeting process until you are sure that all issues have been identified and documented. 10. Present the completed business requirements document to all stakeholders in a formal meeting. Take notes in order to maintain the collective project memory and be ready to address any issues or concerns which may be raised. Niall Kennedy is an internet marketing consultant. Positive is a UK provider of professional Business Analysis. Contact Positive at http://www.Be-Positive.co.uk for more information about Requirements Documentation. All rights reserved. This article may be reprinted in full so long as the resource box and the live links are included intact. Copyright Be-Positive.co.uk All rights reserved. This article may be reprinted in full so long as the resource box and the live links are included intact. Copyright Be-Positive.co.uk Read more Articles on Top7 or 10 Tips at FileBlogs.com
Article URL

See All articles From Author

For Authors »

For Everyone »

Free Newsletter »

Member Login »

Directory »

Ten Top Tips for Creating Good Business Requirements