4. Reaching the scoping conclusion – the Functional Specification
The scoping work usually involves the three initial steps mentioned and this all helps shape the Functional Specification document. This typically includes details regarding:
– Recommendations for the information architecture
– Identifying and specifying the required functional elements, including any integration required with third-party systems
– The approach that will be taken to meet accessibility requirements
– Wireframes – All the key wireframes to map out the user experience
– The recommended CMS solution
– Production schedule: This is usually in the form of a Gantt Chart. It is the schedule for each element of the project to meet the required deadline, with clear milestones, linked to progress review meetings.
– The post-launch KPIs (Key Performance Indicators) to measure success
– Service level Agreements for: support, hosting and digital marketing (if required)
To conclude, to skimp on the website scoping process, perhaps because of a sense of project urgency, is to ‘marry in haste and repent at leisure’. A project that has been properly scoped is much more likely to run smoothly and be delivered on time and on budget.