Viewing Posts by Mike Frenette
It's great to on the bleeding edge sometimes, isn't it? I was fortunate enough to be invited to meet with Jordan Kyriakidis, CEO of QRACorp in my home town of Halifax, Nova Scotia when he saw I was speaking at the annual Professional Development Symposium. Jordan introduced me to the concept of Natural Language Processing as it applies to requirements documents. Jordan and I (well, mostly Jordan) put on a webinar today to discuss this very topic. You can view it here on projectmanagement.com.
Here's a handy shortcut: http://bit.ly/reqswithNLP.
But sometimes it is easier to read about things, so I thought I'd talk about it here at a high level, at least.
Natural Language Processing is gaining a lot of attention these days. Automatically going through documents and looking for patterns or comparing to knowledge bases, or comparing one document to another to see if they relate one to the other are just a few things NLP can be used for.
Imagine a world where a computer application reads a document instead of you and points out all the places where the requirements writer has been too vague, imprecise, or has not provided enough detail? How about one that compares all the requirements documents in the organization and lets you know when it detects inconsistencies between your work and others? Or maybe one that knows the jargon of the profession in which you work, and can point out misuse of terms? Or one that is able to look through your requirements and tell you what is missing?
Seem like it might be a bit of a stretch? Well, some of what was covered in today's webinar is not available ... yet. But some of it is. And that's what bleeding edge is all about, isn't it? Working with new concepts, innovating new methods and the tools to go with them, envisioning the future.
Now you can decide for yourself whether the webinar might be worth a listen.
Many thanks to Jordan Kyriakidis for sharing this advanced knowledge.
P.S. Below are some comments which I thought were quite generous and gratifying from the over 1,200 attendees:
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!
This Blog is about requirements management, so a book I read recently about Agile tools seemed to apply since some of them are about managing the Product Backlog.
"Actionable Agile Tools" is the name of the book, and it was written by Jeff Campbell. It is a short book - a compendium of tools he has developed over the last ten years as a Scrum Master and Agile Coach. Jeff is Canadian, but has been living in Sweden for many years. I met Jeff at an event called a "Scrum Beers", which is a gathering of people who use Agile. They meet for presentations, followed by some informal networking and libations. Scrum Beers is really about Agile, not just Scrum, and is now present in three countries. Check it out at www.scrumbeers.com.
If you buy the book at http://leanpub.com/actionableagiletools, you can tweet about it at #actionableagiletools.
So - on with my review!
First of all, I must say that Jeff has given some innovative names to some of the tools he mentions. I hope you enjoy the names as much as much as I did. The book is simply structured with a brief introduction and then a chapter on each of the tools. I’ll comment on each of them, but of course you really won’t see the whole picture until you read the book.
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: