RE: Scope Documents

[Shawn Everett]

It was really my own fault.  I didn't do a proper SoW for a large to me
($50k) project.

I've been rather lazy lately.  The client massively increased scope on me
and then held the money ransom.  My quote included a rather vague item of:
Server setup for $X.  They took server setup to include a whole lot of
extra work. :(

Not having proper project documentation meant my ability to fight was
somewhat limited.  Good lesson for me, not to be lazy.  Normally I deal
with great clients and this isn't an issue.

Would you be interested in sending me yours off list to review?

Shawn

> How were you burned?
>
> My own PSA is 5 pages, and each SoW is about 4 pages.
>
> Regards,
>
> Michael B. Smith
> Consultant and Exchange MVP
> http://TheEssentialExchange.com
>
>
> -Original Message-
> From: Shawn Everett [mailto:sh...@tandac.com]
> Sent: Tuesday, February 01, 2011 7:52 PM
> To: NT System Admin Issues
> Subject: Scope Documents
>
> Hi All,
>
> After recently being burned by a client/project, I'm trying to come with a
> new and better scope document.  Could you please review the sample below
> and provide feedback for things that are missing?
>
> I'm specifically looking for assumptions and disclaimers that would be
> important to include in almost any scope document.
>
> Shawn
>
> ===
> Project Scope Document
>
> Purpose: Describe in simple terms what the project is all about.
>
> Project Activities: (steps needed to complete project) for example:
> - Upgrade firmware and drivers on the new servers
> - Install Windows 2008 R2 on both servers
> - Install Exchange 2010
> etc.
>
> Project Deliverables: (What are we going to build)
> - A working email server
>
> Project Completion: (The project is complete when)
> - Email from the Internet reaches each mailbox
>
> Project Assumptions
> All requested software will run correctly.
>
> Workstations are free of viruses, spy-ware or other defects that would
> prevent them from being joined to the domain or working correctly.
>
> Network printers will have server compatible drivers.
>
> Old Anti-Virus can be removed easily from each PC.
>
> Disclaimers
> 1.Items that fall out of the "deliverables" phase and cannot be easily
> quantified in the "completion" phase are considered out of scope and will
> be billed separately.
>
> 2.Existing client technology that is incompatible with the solution
> offered above will be handled on a case by case "best effort" basis and
> billed separately.
>
> 3.Custom software except for Noratek built software, is considered
> outside scope.
>
> 4.If a problem comes up that affects a project completion guideline or
> project deliverable and it has been covered as a project assumption, the
> particular guideline/deliverable will be nullified.
>
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
>



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Scope Documents

[Michael B. Smith]

How were you burned?

My own PSA is 5 pages, and each SoW is about 4 pages.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com


-Original Message-
From: Shawn Everett [mailto:sh...@tandac.com] 
Sent: Tuesday, February 01, 2011 7:52 PM
To: NT System Admin Issues
Subject: Scope Documents

Hi All,

After recently being burned by a client/project, I'm trying to come with a new 
and better scope document.  Could you please review the sample below and 
provide feedback for things that are missing?

I'm specifically looking for assumptions and disclaimers that would be 
important to include in almost any scope document.

Shawn

===
Project Scope Document

Purpose: Describe in simple terms what the project is all about.

Project Activities: (steps needed to complete project) for example:
- Upgrade firmware and drivers on the new servers
- Install Windows 2008 R2 on both servers
- Install Exchange 2010
etc.

Project Deliverables: (What are we going to build)
- A working email server

Project Completion: (The project is complete when)
- Email from the Internet reaches each mailbox

Project Assumptions
All requested software will run correctly.

Workstations are free of viruses, spy-ware or other defects that would prevent 
them from being joined to the domain or working correctly.

Network printers will have server compatible drivers.

Old Anti-Virus can be removed easily from each PC.

Disclaimers
1.  Items that fall out of the "deliverables" phase and cannot be easily
quantified in the "completion" phase are considered out of scope and will be 
billed separately.

2.  Existing client technology that is incompatible with the solution
offered above will be handled on a case by case "best effort" basis and billed 
separately.

3.  Custom software except for Noratek built software, is considered
outside scope.

4.  If a problem comes up that affects a project completion guideline or
project deliverable and it has been covered as a project assumption, the 
particular guideline/deliverable will be nullified.



~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Scope Documents

[Shawn Everett]

Hi All,

After recently being burned by a client/project, I'm trying to come with a
new and better scope document.  Could you please review the sample below
and provide feedback for things that are missing?

I'm specifically looking for assumptions and disclaimers that would be
important to include in almost any scope document.

Shawn

===
Project Scope Document

Purpose: Describe in simple terms what the project is all about.

Project Activities: (steps needed to complete project) for example:
- Upgrade firmware and drivers on the new servers
- Install Windows 2008 R2 on both servers
- Install Exchange 2010
etc.

Project Deliverables: (What are we going to build)
- A working email server

Project Completion: (The project is complete when)
- Email from the Internet reaches each mailbox

Project Assumptions
All requested software will run correctly.

Workstations are free of viruses, spy-ware or other defects that would
prevent them from being joined to the domain or working correctly.

Network printers will have server compatible drivers.

Old Anti-Virus can be removed easily from each PC.

Disclaimers
1.  Items that fall out of the “deliverables” phase and cannot be easily
quantified in the “completion” phase are considered out of scope and will
be billed separately.

2.  Existing client technology that is incompatible with the solution
offered above will be handled on a case by case “best effort” basis and
billed separately.

3.  Custom software except for Noratek built software, is considered
outside scope.

4.  If a problem comes up that affects a project completion guideline or
project deliverable and it has been covered as a project assumption, the
particular guideline/deliverable will be nullified.



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin