Document Delivery

Brad Egeland is an IT/project management consultant and author with over 25 years of software development, management and project management experience leading initiatives in manufacturing, government contracting, gaming and hospitality, retail operations, aviation and airline, pharmaceutical, start-ups, healthcare, higher education, not-for-profit, high-tech, engineering and general IT.

  CRM   Quality   Stakeholder Management   Testing/Test Management  

In the grand scheme of things while running a project, delivering a perfectly formatted, error-free and absolutely grammatically correct risk management plan is probably not at the top of your list. I can understand that. How many of you project management readers out there have heard moaning and groaning from your team members about producing or even proofing plan documents? It’s not the “fun” work on the project. And it doesn’t seem--on the surface--to be the type of work that really adds much value (if any) to the end solution. It’s like when your kids ask, “Why do I have to learn this math? I’ll never use it again.” Sometimes, you have a hard time disagreeing with them, right?

In school, I hated to turn anything in misspelled or with handwriting that didn’t look how I wanted it to. It took me a long time to ever start using pens because I always wanted to be able to erase and correct (okay, I may have been a little OCD about that). Even with my articles, I run them through spell checkers first--though that doesn’t catch a correctly spelled word that may be out of place or out of context. I try to re-read everything, but sometimes things slip through.

But when we’re turning in documents--ones that are actually deliverables on a project--to our customer, we need to consider what they’re seeing …

Please log in or sign up below to read the rest of the article.