Episode 392: Face it. Your Project Requirements are Poorly Written! (Free)

Play Now: For your Project Management Professional (PMP)® exam use PMP exam prep on your phone with The PM PrepCast: Jordan Kyriakidis, CEO of QRA Corp My goal of having these show notes on the website is to give a quick and concise introduction of the podcast topic and to tell you what you can expect to learn from it. Sometimes I am right on point and sometimes I’m a little more vague. And tomorrow, when you are back at the office working on your project requirements your goal will be to correctly and succinctly describe the requirements for that project your company is going to launch. The big difference here is that your descriptions have to be 100% on point. You cannot afford to be vague, because requirements that can be misinterpreted is a sure-fire way to doom your project. So what can you do to improve your requirements? The problem of poorly written, ambiguous, and inconsistent requirements is something that Jordan Kyriakidis (https://www.linkedin.com/in/jordankyriakidis/) has thought about a lot. And his answer to this problem is not only a list of “21 Top Tips for Writing an Exceptionally Clear Requirements Document” (https://qracorp.com/write-clear-requirements-document/) but also to use computing power. Yes, there is actually a software that will scan your requirements document and tell you what's wrong with it. But we’re not going to talk about the software much, because that would be pretty boring here on an audio podcast. Instead, Jordan and I look at the root causes of poorly written requirements and then we introduce you to the most important 6 out his 21 tips. In that way you can start using your brain power to write better requirements. Episode Transcript Podcast Introduction Cornelius Fichtner:   Hello and welcome to Episode #392. This is the Project Management Podcast™ at www.pm-podcast.com and I’m Cornelius Fichtner. My goal here during the first ninety seconds of every podcast episode is to give you a quick and concise introduction of the podcast topic and to tell you what you can expect to learn from it. Sometimes I am right on point and sometimes I’m a little bit more vague. And tomorrow when you are back at the office working on your project requirements, your goal will be to correctly and succinctly describe the requirements for that project your company is going to launch. The big difference here is that your descriptions have to be 100% on point. You cannot afford to be vague because requirements that can be misinterpreted, well they are a sure fire way to doom your project. So what can you do to improve your project requirements? Are you PMP certified and want to earn 37 PDUs quickly and for less than $6 per hour? That’s no problem with the Agile PrepCast. It not only prepares you for your PMI-ACP Exam but also qualifies for a ton of PMP PDUs. Log on at www.AgilePrepCast.com/pdu for the details. The problem of poorly written, ambiguous and inconsistent requirements is something that Jordan Kyriakidis has thought about a lot and his answer to this problem is not only a list of the 21 top tips for writing an exceptionally clear requirements document but also to use computing power. Yes there is actually a software that would scan your requirements document and tell you what’s wrong with it but we’re not going to talk about the software all that much because that would be pretty boring here on an audio-only podcast. Instead, Jordan and I looked at the root causes of poorly written requirements and then we introduced you to the most important six out of his 21 tips. That way, you can then start using your brain power to write better requirements. And now, following this very badly written introduction, please enjoy the interview. Female Voice:   Project Management Podcast Feature Interview. Today with Jordan Kyriakidis, CEO and co-founder of QRA Corporation. Cornelius:   Hello, Jordan and welcome to the Project Management Podcast™ Jordan:   Hello, Cornelius. It