Web Development · Advanced level

Advanced level · Module 5: Client Web Projects and Maintenance · Lesson 1 of 4

Discovery and Scoping

Understand what a client really needs, agree the scope and record it clearly.

In this lesson you will

  • Run a discovery conversation with a client
  • Write a scope with inclusions, exclusions and assumptions

Key concepts

discovery questionsgoals and audiencescopeassumptions and exclusions

The lesson

Clients often ask for a website when their real goal is more enquiries, fewer phone calls or donor credibility. Ask about goals, audiences, existing materials, who will update content, budget and deadlines.

Write the scope: pages and features included, what is excluded (for example logo design or copywriting) and assumptions (the client provides photos by a date). Clear exclusions prevent disputes.

Agree how success will be measured — enquiries per month, time saved — so both sides know whether the project worked.

Step by step

  1. Prepare discovery questions for the practice client.
  2. Run a discovery conversation and take notes.
  3. Write the scope with inclusions, exclusions and assumptions.
  4. Agree success measures.
Case study

Scoping a website for a youth NGO in Juba

A composite, illustrative case showing how discovery changed what was built — and what was deliberately left out.

Context

A youth NGO in Juba (a composite example based on common situations) asked a freelance developer for 'a modern website with a members' portal'. It had a small budget, a Facebook page and one part-time communications officer.

Challenge

The request was large and vague, the budget small and nobody on the team had time to manage a complex system after launch.

What they did

  1. Ran a discovery meeting and learned that the real goals were donor credibility and fewer phone calls asking about programme dates.
  2. Proposed a fast, five-page site on a simple CMS the communications officer could update, with an events page and a contact form.
  3. Listed the members' portal as an exclusion for phase 1, with an estimate for a later phase if needed.
  4. Agreed a content checklist with deadlines and a one-hour training session at handover.

Results

  • The site launched on time and within budget, and the officer updated events without help.
  • Phone enquiries about dates dropped because the events page answered them.
  • Six months later the NGO chose to fund a simple volunteer sign-up form instead of a full portal.

Lessons for your own work

  • Discovery reveals goals that are often smaller and clearer than the first request.
  • Written exclusions protect both client and developer and make later phases easy to sell.

Practice activity

Produce a scope document for the practice client.

Expected result: A scope the 'client' confirms, with clear exclusions and success measures.

Check your understanding

  1. Why list exclusions in a scope?

    Show answer

    To prevent misunderstandings about what is and is not included.

  2. Give an example of a project goal beyond 'a website'.

    Show answer

    For example, more course enquiries or fewer phone calls about opening hours.

Taught live by an instructor — online or in person. Free course lessons are for self-study and do not lead to a certificate — see registration options.