Scoping Tamar Design and Build Projects
Although the majority of our business at Tamar is natural search conversion, we are often commissioned to redesign our client’s web and micro sites.
In many cases the sites we are asked to redesign have been built without SEO in mind and therefore building the site from the ground up i.e. User Centered Design twinned with Accessible HTML/CSS is the best solution.
Q Why is a User Centered Design and Accessible HTML/CSS approach so valuable to our clients?
A Because this approach allows for the foundations for onsite search optimisation to be in place.
Today’s project manager (PM) tips will highlight some important aspects of writing a scope of works for a typical redesign project.
Firstly let’s look at the definition of the Scope of Works (SOW).
Scope of Works
The SOW is a working document that details the project objectives, deliverables, budget, timescales, exclusions and assumptions. Ideally this will act as the central project document describing the scope of the works between Tamar and the client.
The SOW will be revised until both parties are satisfied and ready to sign off.
This document is your main point of reference should you need to check what is in or out of project scope. The SOW acts as the basis for managing all change within the project should Tamar and the client decide to raise a change request.
When producing your SOW, approach this like a criminal investigation document i.e. the more questions you ask your Usability, Design and Development team, the more accurate your scope becomes, even if you have to question your main suspects until your blue in the face. It is the role of the PM to leave no stone unturned.
Update your SOW with all changes no matter how big or small and all ask your client to acknowledge receipt and sign-off all revisions.
When you think you have included too much detail into your SOW, start your Project Specification.