Be warned, this is a little rant post, about what a “scope of work” document or statement entails.  Sorry folks, I am may be a little frustrated, mainly because my sound board decided to go on leave…  bless her soul!

scope of work

BACKGROUND

By nature, I am a ENTP.  That means I’m not phased by details, but rather inspired by vision and what something could potentially be – in the future.  I am big picture kind of person.  Minor details, are simply that, minor.  It is something that can be fixed, preferably by someone else, when I am off on my next big adventure.  I am a strategist.

The thing is, if you put someone like me in a position where small details really matter, I do one of two things.  (1.)  I become really fussy and irritating about small, minor detail or (2.) I throw my toys and give up.  (Perhaps number 2 is a little extreme).

OUT OF SCOPE

Here’s the thing, when you’ve been working on a project for THREE years, you’re kind of passionate (and gatvol) of the project.  But when the development team ‘just wants to sign off‘ on phase 2 of the project and throws in words like “it is out of scope” and “requires additional development” followed by “no we can’t give you timelines” it is highly frustrating.

SCOPE OF WORK

We can get all fancy with the definitions of a scope of work, however that’s not going to benefit anyone.  Bottom line, the scope of work, is a defined guideline of the work that needs to be done.  Bright Hub Project Management goes as far as to call it a RULE BOOK.  In other words, the law!

  • CLEARLY DEFINED means, we take the time to analyse and understand what the client’s needs are.
  • It also means we need to be super specific about what we say in the document and avoid anything ambiguous.
  • A scope of work includes things like objectives, standards, risks and regulations.
  • It is a document.  Not a verbal agreement or an email with a couple of bullet notes.
  • It is also a document that is shared among and reviewed throughout the project, even when all the relevant parties were not involved in the initial scoping.
  • And amazingly, if it was done thoroughly and correctly, comes in quite handy!

A scope of work is not, a card you play and a tool you use to “wing” things, at the end of the project when you’re gatvol.

Next time, we can look at the definition, roles and responsibilities of a PROJECT MANAGER.  Trust me, if I start now, I may not stop!

So, how was your day, today?

Share and bookmarkShare on FacebookTweet about this on TwitterPin on PinterestShare on LinkedInBuffer this pageShare on Google+Digg thisShare on StumbleUponFlattr the authorShare on RedditShare on TumblrPrint this pageEmail this to someone

Leave a Reply

Your email address will not be published. Required fields are marked *