3 Ways Project Documentation Can Run Amok

From the pmStudent Blog
by
Ranting and raving about project management and systems engineering.

About this Blog

RSS

Recent Posts

The Problem with Project Management

The Problem with Project Management

The Problem with Project Management

LinkedIn Recommendations Are Easy

The Catch-22 of Project Management Certification and Experience

Email Notifications off: Turn on


We all know documentation can be useful and is an important part of project management.

But all too often, we go too far.

Here are just a few ways your own project documentation can run amok.  Seek out and destroy them.

Relying on Documentation for Communication

It's always so strange to me when I hear someone justify a lack of communication by saying they assumed everyone knew about it, because it was on page 734 of the software design document.

Really?

My first question is why the hell we have a software design document with 734 or more pages?

Second, exactly what mechanism do you think is at play that would allow all stakeholders and team members to be aware of every update to all the documentation on your project?  Did I miss the memo about the new matrix-style jacks so we can all plug in and download information directly into our brains?

When I talk about communication, face-to-face is always preferred, followed by phone, then email.  Communicating via documentation is not even on my list because it's not a method for communicating.  It's for documenting.

Ask yourself...is this information best used as a book is used?  Is it something that needs to be documented so it can be learned by someone new, years down the road?  Are you trying to shove a bunch of stuff into it that could best be communicated in another way?

Producing Documentation that Provides No Value

When it seems you are putting more time and effort into writing documentation than actually producing a product, it's time to ask yourself what value that documentation is providing.

Every section of every document should have a purpose.  It should have a user.  If there is no user, there is no purpose.  Who is going to read this thing?

User stories can be wonderful for identifying the value for documentation, and specific sections within documents.  If you're not familiar with user stories, they are simple.  Use the following syntax.

"As a [user] I want [something] so that [benefit]."

I encourage you to create a set of user stories for every document you have.  Go show them to the users and validate you actually know what the [bleep] this is being used for.  It  will be an enlightening experience.  I have gone through this activity and cut 60-page management plans down to 8 pages in length, without losing any value.  In reality, the organization actually gained value because someone might actually read an 8-page document.

I have come into organizations and found documents that have taken on lives of their own.  When I ask why a particular activity is being performed because I don't see what it's used for, I am told "it's for the TPS report".  When I ask who reads the TPS report the answer is "I don't know."

Hmm.  Let's stop doing it, and see if we get any phone calls.

Producing Documentation as an Alternative to Trust

Do you ever get the feeling some things are documented just so someone can point a finger and say "I told you so!" or "You should have known better!"

Documentation (and process) is no alternative to trusting people to do the right thing.  A classic example is the case where a simple point-to-point communication step in a process is turned into a frankenstein monster.  I once was on a project where an update to configuration-controlled artifacts was implemented by a specific individual.  After changes to the project were formally approved, this person would update the baseline.

The 'trigger' to have this person look for the completed change request and update the baseline could be as simple as "give Jasmine the CCR number and ask her to update the baseline."  Instead, a whole new tool was set up so that timestamps could be saved and requests would be formally documented.  Mind you, this is completely separate from the system used to actually run the change control process.

In the end, this insanity resulted in pages upon pages of documentation about the new system and all of the scenarios that could possibly every happen.  There was no trust in the people running the process in the first place; and no trust that people on the project had enough brain power and common sense to fiture out what to do in case things didn't go smoothly.

Trying to document every 'what if' scenario is as futile and worthless as trying to manage every risk.  Only a handful of scenarios are worth the time and effort to plan for.  Like the one that mud people will emerge from the bay and raid our server rooms, frying server after server with their muddy slime and killing our project.

Damn mud people.

 

images by A.K. Photography and ChernobylBob

 

Share this with your network
Posted on: December 10, 2010 10:23 PM | Permalink

Comments

Network:182



I met someone recently who said, "It might be my job to write documentation, but it's not their job to read it." I thought this was great, and it's something we should bear in mind when creating paperwork - what are we doing it for and how can we make it easy for the people who are going to have to use it?

Network:81



I like it!


Another twist on it would be "It's my job to write documentation that people can ACTUALLY read if they have a need to."


Cheers!


Josh Nankivel

pmStudent e-Learning

Please Login/Register to leave a comment.

ADVERTISEMENTS

A celebrity is a person who works hard all his life to become known, then wears dark glasses to avoid being recognized.

- Fred Allen

ADVERTISEMENT

Sponsors

>