ICPM

This email address is being protected from spambots. You need JavaScript enabled to view it. This email address is being protected from spambots. You need JavaScript enabled to view it. The International Community for Project Managers
Brought to you by TenStep, Inc.
2363 St. David's Square
Kennesaw, GA 30152
877-536-8434 or 770-795-9097

This email address is being protected from spambots. You need JavaScript enabled to view it.
You are here: Home Blogs Episode 392: Face it. Your Project Requirements are Poorly Written! (Free) #PMOT
Monday, 19 June 2017 03:17

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

Written by 
Rate this item
(1 Vote)

392Click Here to Listen to the Interview: http://bit.ly/2s3LsEJ
Read More: http://bit.ly/PMPodcast392

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

Read 566 times

Cornelius Fichtner, PMP is a Project manager, PMP trainer, host of The PM Podcast, creator of the PM Prepcast, PDUCast, public speaker and gummi bear addict.

Website: www.cornelius-fichtner.com
Login to post comments

News and Promotions

Keep up to date with the latest happenings by signing up for our newsletter. Subscribe below.

Twitter Update

Who's Online

We have 338 guests and no members online

Got something to say?