Risk Management

How to Accomplish Requirements Management Successfully?

Requirements management allows companies to document, analyze, prioritize before and after a project starts. Interestingly, a PMI report informs that 47% of projects fail due to faulty requirements. In this article at Project Risk Coach, Harry Hall suggests ways to accomplish requirements management successfully.

What to Do and Not Do for Requirements Management

There are several things that are necessary as well as optional for requirements analysis. Here is a list of things that you should and should not do while you are working on requirements management:

Do’s:

  • Involve the right stakeholders. Within a ‘matrix environment’, project managers should take stakeholder approvals for resources early.
  • Understand the importance of the features. 45% of product features are never used, as per a Standish Group study. Ask how the features are important for the product and if it is in line with the project goals.
  • Confirm the credibility of requirements. A senior stakeholder may ask for a requirement in passing. Confirm with the higher management or PMO how to tackle this type of requests.
  • Make the requirements visible. Use tools like diagrams, use cases, stories, etc. for easy understanding of the stakeholders.
  • Maintain a version for each change in the requirements. You should understand how the requirements changed from the initial stages to the current. Tools are available for effective requirements management.

Don’ts:

  • Do not overdo it. Though requirements management needs project managers and business analysts to stay alert, you need not oblige every requirement.
  • Do not store information in different places. Collate all the emails, spreadsheets, post-its, minutes, etc. in one place for easy reference. Ensure that all files and information related to the project is saved in one location.
  • Do not write vague requirements. Provide specific instructions that would be easier to follow.
  • Do not make the design expectations too detailed when you write the requirements.
  • Use a standard tool for requirements management. If you do not have any, convince the PMO or senior management to get you one.

To view the original article in full, visit the following link: https://projectriskcoach.com/five-things-to-start-and-five-things-to-stop-in-requirements-management/

Tags

Indrani Roy

Indrani Roy is currently working as a Content Specialist for CAI Info India. She has knowledge in writing blogs, product descriptions, brand information, and coming up with new marketing concepts. Indrani has also transcribed, subtitled, edited, and proofread various Hollywood movies, TV series, documentaries, etc., and performed audio fidelity checks. She started her career by articulating a knowledge base for an IT client, and, eventually, went on to create user manuals and generate content for a software dashboard. Writing being one of her passions, reading books is naturally her favorite pastime. When not lost in the world of letters, she is a foodie, movie buff, and a theater critic.

Related Articles

Back to top button
Close
X

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.