Cornelius Fichtner help you with your PMP Exam Prep (https://www.project-management-prepcast.com) as well as earn free PDUs (www.pm-podcast.com/pdu). Passing the PMP Exam is tough, but keeping your PMP Certification alive is just as challenging. Preparing for the exam requires an in-depth study of the PMBOK Guide and dedicated study discipline. And once you are PMP certified, then you are required to earn 60 Professional Development Units (PDUs) every 3 years to keep your certification alive. Let me help you make this journey easier with tips and tricks on how to prepare for and pass the exam as well as efficiently earning your PDUs once you are certified.
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.
Thanks for this. I had to google "21 Top Tips for Writing an Exceptionally Clear Requirements Document" to follow along with this podcast. Would be helpful in future if a quick link was provided as it adds more value and something to help follow along with.
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I listened to this the other day. An important topic. I was glad to hear I cover much of these items already!
I have used QVscribe before - last year I believe.
Mohamed Abdelaziz MohamedConsultant Senior Engineer| Expertisehouse for ConsultantingAlex, Alexandria, Egypt
Thanks
Mansoor MustafaSenior PM| Government DepartmentRawalpindi Punjab, Pakistan
