1. Large D&B process

2. Framework - deliverables Contract Budget Timeplan SOW BriefSpecificationProductGo liveProject review Initiate Explore Concept Produce Release Review Requirements log Technical review KPI framework Ambition document Summary presentation Sitemap Annotated wireframes Taxonomy Content audit KPI metrics Tagging schema Style tiles Template designs Design kit QA test plan Analytics review 2% 11% 18% 4%1% 64% Budget guideline: Risk log Launch plan

3. Documents are for thinking, not just filling in

4. Make the tough calls early

5. You can’t do everything you want to in the first release Zoneit wants

6. Progressive enhancement, not graceful degradation

7. Use the same language

8. Initiate Set up project in Timezone including any add-ons Follow D&B checklist and ensure SoW convers all points Set up appropriate PM tool: Agile Jira / AgileZen / Basecamp Internal kick off Client kick off Risk log – List of all potential project risks, status and mitigation plans. To keep updated throughout project (PM)

9. Explore Activities to include workshops, interviews, data analysis and document review Requirements log – List of prioritised business and user requirements with internal estimates of time. Explicitly states which are in/out of scope (PM/BA) KPI framework – How we’ll measure success. Doesn’t necessarily include specific metric and rarely (at this stage) includes explicit targets e.g. Engagement, probably measuring downloads, no target set yet (Strategy) Technical review – Proposed approach to / details of hosting, architecture, CMS, 3 rd party integrations (Tech) Ambition document – Project principals / goals Summary presentation – Outline of work carried out and findings. Summarises other docs

10. Concept Sitemap – Site navigation structure but not all pages. Named template for each page (UX) Annotated wireframes – For every template on desktop. At least 20% of them for mobile. Common elements page e.g. WYWIWYG styling options (UX) Taxonomy – Tagging structure and initial list of tags / categories (UX + Editorial) Content audit – Review of site content, recommendation on cut / keep / rewrite (Editorial) KPI metrics – Evolution of KPI framework with specific metrics e.g. downloads, likes (Strategy) Tagging schema – Analytics tagging plan for event tracking, goals, funnels etc. (Strategy) Style tiles – Look and feel for site (UX)

11. Produce Template designs – Designs for minimum 50% of templates, desktop (UX) Design kit – All page elements and action states e.g. buttons, links, images, roll overs (UX) QA Test plan – Quantity, types and timings of testing. Test script, entry/exit criteria (Tech)

12. Release Activities to include checking analytics working, especially event tracking Launch plan – Document outlining key actions (e.g. moving from staging server to live, repointing IP), timings, owner and status

13. Review Analytics review – At least 1 review of analytics data post go-live to measure results against objectives (Strategy)

14. Proportion of project days by department 49% Technical scoping Back endFront endQABug fixing 25% ResearchIAVisual design 21% Project management Account management 5% StrategyEditorial Creative campaigns (+/- 4%)