Ever wonder if the requirements you are writing make sense? Do you wonder about what you could do to improve them? Make them more concise? More accurate?
I ran across a company recently that has developed a new approach to this with a product that scans the requirements you tag in your document and tells you what might be improved. The product is quite new, and they are looking for beta testers if you are interested. You can sign up at https://qracorp.com/
Have you had experiences with similar tools? Or is this approach using natural language processing new to you? Comments welcome!
You Don't have Requirements!
Categories: Project Requirements
PMI Releases Business Analysis for Practitioners: A Practice Guide - free download for the next 6 months!
Did you know that according to research PMI conducted in 2014 that only 64% of completed projects met their original goals and business intent? That 16% of projects in the last 12 months were failures? That 37% of organizations reported "inaccurate requirements gathering" as the primary cause of project failure? That poor requirements management practices are the second leading cause of project failure, second only to changing organization priorities?
Thankfully, good business analysis on projects and programs result in customer expectations being met, engaged and committed stakeholders, projects that are more likely to be delivered on time and within scope and budget, implemented solutions that provide business value and meet stakeholder needs, all while developing reusable business analysis competencies for future projects.
The above are quotes and paraphrases from the recently released the Project Management Institute's 227 page Business Analysis for Practitioners: A Practice Guide. It is available for free download for the next six months. Written by experts in the field, it is chock full of solid tools and techniques to help you succeed on your projects and programs in the area of business analysis and requirements management.
Why not get it today and learn more about Needs Assessment, Business Analysis Planning, Requirements Elicitation and Analysis, Traceability and Monitoring and Solution Evaluation? From SWOTs and Five Whys to Use Cases and Wireframes, and everything in between, you will be glad you did!
And keep an eye on this Blog for possible posts by some of the Practice Guide's core and review committee members, among them Elizabeth Larson, Rich Larson and Ellen Gottesdiener.
Get your free copy here for the next six months at this link:
My colleague Beth Ouellette and I had a little fun at the Phoenix PMI Congress with our presentation of Top Tips for Effective Requirements Management collected through a survey of the 18,000 member Requirements Management Community of Practice and through the webinars presented to the Community over time. We thought we would liven things up a little by presenting short vignettes acted out by volunteers from the audience. Following are the names of the skits with a brief explanation of what they were meant to convey. The first five convey project issues. The rest show actions you can take to manage requirements to help drive project success.
We wrapped up the session with the seven keys to requirements management success:
What has been your experience with the impact of requirements on your projects? Have you experienced any of the project and requirements issues we tried to get across with our humourous skits? Maybe you were at the session in Phoenix and have something you'd like to add.