<?xml version="1.0" encoding="UTF-8"?>
<report>
  <author>Sonia Kay and Ashley Friedlein</author>
  <body-uk-format>econsultancy_xml</body-uk-format>
  <body-uk-formatted>&lt;h2&gt;Overview&lt;/h2&gt; 
&lt;p&gt; 
&lt;strong&gt;Web Project Template Files:&lt;/strong&gt; Project Definition and Start Up &lt;br /&gt;
&lt;strong&gt;Authors:&lt;/strong&gt; Sonia Kay, Econsultancy and other expert contributors&lt;br /&gt;
&lt;strong&gt;Title:&lt;/strong&gt; Technical Specification
&lt;/p&gt;&lt;h2&gt;About this Guide&lt;/h2&gt; 
&lt;p&gt; 

For project managers, and certainly the programming team, it is important to try and get the technical specification right first time.  Whereas many of the other elements can be changed even at a late stage if absolutely necessary, or are subject to interpretation, the technical specification contains only hard facts. A mistake in the technical specification is quite unequivocally a mistake and can cause havoc in a project.
&lt;/p&gt;&lt;p&gt;
The Technical Specification Content List is a MS Word document that contains a list of the content that you would expect to be detailed within a technical specification.  As such the document can be used as a checklist to ensure that the important parts of the technical build are correctly specified during development.
&lt;/p&gt;&lt;p&gt;
Note: the Technical Specification may also form a Schedule to the Contract (see Section 2.9.1)
&lt;/p&gt;</body-uk-formatted>
  <body-uk-unformatted>&lt;FormattedContent xmlns="http://www.e-consultancy.com/schema/formattedContent/"&gt;&lt;Subhead&gt;Overview&lt;/Subhead&gt; 
&lt;Paragraph&gt;&lt;/Paragraph&gt; 
&lt;Emphasis&gt;Web Project Template Files:&lt;/Emphasis&gt; Project Definition and Start Up &lt;LineBreak&gt;&lt;/LineBreak&gt;
&lt;Emphasis&gt;Authors:&lt;/Emphasis&gt; Sonia Kay, Econsultancy and other expert contributors&lt;LineBreak&gt;&lt;/LineBreak&gt;
&lt;Emphasis&gt;Title:&lt;/Emphasis&gt; Technical Specification
&lt;Paragraph&gt;&lt;/Paragraph&gt; 
&lt;Subhead&gt;About this Guide&lt;/Subhead&gt; 
&lt;Paragraph&gt;&lt;/Paragraph&gt; 

For project managers, and certainly the programming team, it is important to try and get the technical specification right first time.  Whereas many of the other elements can be changed even at a late stage if absolutely necessary, or are subject to interpretation, the technical specification contains only hard facts. A mistake in the technical specification is quite unequivocally a mistake and can cause havoc in a project.
&lt;Paragraph&gt;&lt;/Paragraph&gt;
The Technical Specification Content List is a MS Word document that contains a list of the content that you would expect to be detailed within a technical specification.  As such the document can be used as a checklist to ensure that the important parts of the technical build are correctly specified during development.
&lt;Paragraph&gt;&lt;/Paragraph&gt;
Note: the Technical Specification may also form a Schedule to the Contract (see Section 2.9.1)
&lt;Paragraph&gt;&lt;/Paragraph&gt;&lt;/FormattedContent&gt;</body-uk-unformatted>
  <body-us-formatted nil="true"></body-us-formatted>
  <body-us-unformatted nil="true"></body-us-unformatted>
  <created-at type="datetime">2007-09-27T00:00:00+01:00</created-at>
  <expertise-level-id type="integer">1</expertise-level-id>
  <extract-formatted>&lt;p&gt;Need to write a tech spec for a web site? Download this template to save you time. Use it as a checklist to ensure that the important parts of the technical build are correctly specified during development.&lt;/p&gt;</extract-formatted>
  <extract-unformatted>Need to write a tech spec for a web site? Download this template to save you time. Use it as a checklist to ensure that the important parts of the technical build are correctly specified during development.</extract-unformatted>
  <featured type="boolean">false</featured>
  <id type="integer">409</id>
  <image-id type="integer">4269</image-id>
  <legacy-publication-filename nil="true"></legacy-publication-filename>
  <legacy-publication-folder>template-files-technical-specification</legacy-publication-folder>
  <legacy-publication-id type="integer">95962</legacy-publication-id>
  <name>Technical Specification - Web Project Template Files</name>
  <newer-version-of type="integer" nil="true"></newer-version-of>
  <parent-id type="integer">400</parent-id>
  <position type="integer">2</position>
  <price-id type="integer">12</price-id>
  <private type="boolean">false</private>
  <published-at type="datetime">2009-03-01T23:00:00+00:00</published-at>
  <report-category-id type="integer">10</report-category-id>
  <report-category-position type="integer" nil="true"></report-category-position>
  <slug>technical-specification-web-project-template-files</slug>
  <unpublished-at type="datetime" nil="true"></unpublished-at>
  <updated-at type="datetime">2009-08-13T15:14:24+01:00</updated-at>
  <video-id type="integer" nil="true"></video-id>
</report>
