Deliver staged work, priorities, ownership and review records. Produce inspectable outcomes and document the impact and approval of scope changes.
Break the project into reviewable stages with clear priorities, owners and completion criteria, so feedback can inform the next iteration.
Working material
Scope includes pages, content, functions and acceptance methods. Record change impact and decisions, and distinguish demonstrations, tests and released work.
Agile project delivery · Working details
Break the project into reviewable stages with clear priorities, owners and completion criteria, so feedback can inform the next iteration.
Delivery and checks
Trace requirements to actual pages or outcomes and check owners and outstanding items. Provide inspectable evidence rather than a bare completion statement.
Related practical notes
Break the project into reviewable stages with clear priorities, owners and completion criteria, so feedback can inform the next iteration.
Practical notes
Explaining the output of agile training
Describe audience, exercises and feedback, with certificates explained separately. Do not imply accreditation where it has not been established.
Specification comparison
Project discipline
Define specification comparison responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Scope management
Project discipline
Define scope management responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Agile is not a process
Each iteration should produce something reviewable and use feedback to adjust priorities. More meetings without visible pages do not create a useful learning loop.
Practical notes
Social contracts: Working out how to work together
Define disagreement, escalation and revision processes. Return to the task and evidence rather than personal labels during conflict.
Practical notes
Agile ways of working: Continuous improvement through retrospectives
Choose one recurring issue and record its trigger, a controllable change and an owner. Check whether the change happened before adding more improvement commitments.
Practical notes
Our social contract
Explain channels and confirmation at kickoff and refer to the agreement during disagreements. Review whether it still matches real work.
Practical notes
Creating effective teams
Agree who decides, where feedback lives and what completion means. Record disagreements and evidence rather than interpreting silence as consensus.
Related practical notes
Break the project into reviewable stages with clear priorities, owners and completion criteria, so feedback can inform the next iteration.
Practical notes
How to choose the right CMS
Use an article, product and approval as sample tasks. Have real editors author, preview and restore content and record assistance and maintenance costs.
Practical notes
Building a martech stack
Map acquisition, content, email, analytics and customer records, including existing tools. Before adding a system, check export, synchronisation and maintenance ownership.
Practical notes
Plan human review for AI content
Generating a whole website and then looking for someone to check it encourages a rushed review. Decide beforehand which material is available, which statements need approval and who can publish the result. The draft can then be built around information that is possible to verify.
Practical notes
How to create a digital strategy roadmap
Separate current problems, near-term improvements and later experiments, with owners and evidence. Keep the rationale for roadmap changes traceable.
Practical notes
How to perform a website audit
Sample navigation, copy, images, forms, search and mobile tasks. A successful response establishes reachability, not correct content or behaviour.
Practical notes
How to brief a digital agency
State the business, audience, pages, available material and decision-maker. Clarify budget and timing conditions and identify specific reference sections.
Planning headless CMS content
Download this editable planning headless cms content to record current work, open questions and owners. OXOAK examples can be adapted to the project.
Digital product design workbook
Download this editable digital product design workbook to record current work, open questions and owners. OXOAK examples can be adapted to the project.
Practical notes
Why conducting a content audit is essential
Record URL, topic, owner, validity and action. Distinguish duplicates, outdated material and unsupported claims rather than deciding from traffic alone.
