A summary of the goals and tasks to be completed in a release

<Reminders to Read and Delete>

• Work out the primary goals first, then
• Call the client before sending
• Fill in the OWA user name and passwords
• Remember to add:
• "Testing" incident of [XXX] Hours
• "Administration" incident of [XXX] Hours
• Print this document in landscape

</Reminders to Read and Delete>

Dear [XXX],

As per our conversation, the following incidents are included in this Release Plan. The primary goals are:

• [XXX]
• [YYY]

The total estimated cost for this release is $XXX

<Additional Release Text>

Note: This is an additional release that is not part of the original estimate for the project

</Additional Release Text>

Developer Resources

<Replace Details="with relevant resources, rates and employee ID to the link">

</Replace>

Release Review Resources

At the end of each release, Adam Cogan, the SSW Chief Software Architect, will review the work completed to ensure that it conforms to best practices.

Engagement Model <Choose 1 Option>

This release will be completed on and “Time and Materials?model under a short release model (approximately 160 hours).
See more information on the definition at the SSW Terms and Conditions.

Once the above incidents have been completed you will receive a “Test Please?email with the new version for you to test and approve.

Tips:

• You can review incidents by accessing Microsoft Access Outlook.
• Your Project URL: http://cow/exchange/jacklin/Inbox/Northwind/Release02_AccessToSQL
• Your User Name: [XXX]
• Your Password: [XXX]
• Clients that work efficiently with emails enjoy using email more. Test yourself…can you copy a subject above, paste into your MSN (or Google) toolbar and find the email instantly? If not see "How to use the Cool "Windows Desktop Search for Enterprise"

Additional Items:

• Please continue to send additional requests (one email at a time). If you specify “BUG?or ?must be in this release)? then it will be completed in this release, if not then it will be done in the next release.
• It is useful to know how many bugs pop up during the release. Please only use the term "BUG" in the subject if it falls within the "Definition of a Bug".
• In general Release Plans should be approximately 160 hours - 2 weeks with 2 developers (or 4 weeks with 1 developer). If there are "Additional Items" this will increase the hours and cost. See "Do you break work into 2 week blocks"
• Expect some “Additional Items?for bugs ?when discovered we consider them to be part of the current release ?we are always doing our best to eliminate them.
• Expect some “Additional Items?for roadblocks that prevent the developers completing an Incident.
• Expect some “Additional Items?for small things that the developer deems easy to do (like fixing a typo, re-organizing the UI etc). Generally these are tasks that the developer is confident to do within a very short period of time (less than 30 minutes).

Terms and Conditions

• This work will be conducted according to agreed Term and Conditions. If no terms and conditions have been signed yet, the work will be conducted under the standard SSW terms and conditions found here: http://www.ssw.com.au/ssw/Standards/Forms/ConsultingOrderTermsConditions.aspx until a specific terms and conditions is signed.
• The above are estimates only, not a fixed price contract. Work is conducted on a time & materials basis.

----- Report Generation Time: 1 second(s)

----- Generated by SSW eXtreme Emails! Version 16.50
----- The Simplest Project Management System Available
----- www.ssw.com.au/eXtremeEmails/