Large D&B process

Framework - deliverables

Contract

Budget

Timeplan

SOW

Brief Specificatio

n

Product Go live Project 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

Documents are for thinking, not just filling in

Make the tough calls early

You can’t do everything you want to in the first release

Zone it wants

Progressive enhancement, not graceful degradation

Use the same language

InitiateSet up project in Timezone including any add-onsFollow D&B checklist and ensure SoW convers all pointsSet up appropriate PM tool: Agile Jira / AgileZen / BasecampInternal kick offClient kick off

Risk log – List of all potential project risks, status and mitigation plans. To keep updated throughout project (PM)

ExploreActivities 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, 3rd party integrations (Tech)

Ambition document – Project principals / goals

Summary presentation – Outline of work carried out and findings. Summarises other docs

ConceptSitemap – 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)

ProduceTemplate 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)

ReleaseActivities 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

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

Proportion of project days by department

49%

Technical scoping

Back end

Front end

QA

Bug fixing

25%

Research

IA

Visual design

21%

Project management

Account

management

5%

Strategy

Editorial

Creative campaig

ns

(+/- 4%)