RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Larry Medina <[log in to unmask]>
Reply To:
Records Management Program <[log in to unmask]>
Date:
Tue, 20 Nov 2007 16:50:02 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
>  Anybody have any
> cautionary tales taken from actual experience?


Make sure the scope of what you want the consultant/contractor to accomplish
is VERY CLEAR.

The single biggest problem seems to be scope creep, as it impacts both the
total cost and the schedule of any engagement.  It's important to make sure
you know what YOU NEED TO ACCOMPLISH, and that the things that you MAY want
to achieve that extend beyond that don't cloud the effort.

A lot of this involves ensuring all parties impacted by whatever you're
attempting to accomplish have been clearly informed as to what your plans
are and that NO ONE is able to provide input directly to the
consultant/contractor requesting they change, add, or modify in any way what
the original scope statement includes without the project
manager/coordinator being involved.

Also, ensure the chosen contractor has the knowledge, skills, and ability to
accomplish all of the goals of the project natively and doesn't have to
bring in any third parties that they may not have control over their
availability or schedule.  The inevitable finger pointing exercise isn't
worth the concern.

Larry

-- 
Larry Medina
Danville, CA
RIM Professional since 1972

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]

ATOM RSS1 RSS2