Goals and scope: what the project is actually for

By the end, you can

• Distinguish a project's goal from its scope, and explain why a goal without a scope or a scope without a goal is incomplete (PM-1).
• Use AI to draft a first-pass goal statement and in/out scope list from a rough project idea (PM-1).
• Explain why a drafted goal or scope item stays a proposal until the sponsor confirms, edits or rejects it (PM-1).

Before you start

This is Module 1, Lesson 1 of the AI-Powered Project Management course. It assumes you can read an informal request for a project — an email, a chat message, a two-line ask from a sponsor — and have used at least one AI chat assistant for drafting text. It does not require any project-management certification, software or a specific planning tool; tool choice belongs to a later module.

A goal is why; a scope is what

Every project starts as someone's rough idea: "we need a better onboarding process," "let's redo the newsletter," "sort out the storage room." Before any plan, task list or AI draft is useful, that idea needs to become two separate things: a goal and a scope.

A goal is why the project exists — the result the sponsor actually wants, stated plainly enough that you could recognise it happening. The Association for Project Management's project management glossary defines an "objective" as "a generic term for predetermined results towards which effort is directed," adding that objectives "may be defined in terms of outputs, outcomes and/or benefits." In plain terms: a goal names the change, not the activity that produces it. "Run three onboarding workshops" is an activity; "new starters are productive in their role within two weeks" is a goal.

A scope is what is and is not included in the work that gets you there. APM's glossary defines scope as "the totality of the outputs, outcomes and benefits and the work required to produce them" — everything the project will actually touch, named clearly enough that anyone reading it can tell what's in and what's out. APM's guidance on scope management is blunt about why that boundary matters: "clearly defining what is in and out of scope prevents the risk of misunderstanding at a later point in the project that may lead to emerging issues and change requests." A goal without a scope is a wish. A scope without a goal is a task list nobody can explain the point of.

Let AI draft the first pass; keep the sponsor as the decider

A rough idea rarely arrives goal-shaped. This is exactly the kind of drafting work AI does well: given the sponsor's own words, it can propose a candidate goal statement and a first-pass list of what's in and out of scope, in minutes rather than a meeting.

That draft is not the same thing as an agreed goal or an agreed scope. The US National Institute of Standards and Technology's (NIST) AI Risk Management Framework frames an AI system as "an engineered or machine-based system that can, for a given set of objectives, generate outputs such as predictions, recommendations, or decisions" — a generator of candidate outputs, not a party who can decide what your project is actually for. A drafted scope line is a proposal until the sponsor — the person who owns the outcome and answers for it — confirms, edits or rejects it. This is the same human-in-the-loop discipline the Open Worldwide Application Security Project's (OWASP) guidance on excessive agency recommends more broadly for AI-connected systems: "utilise human-in-the-loop control to require a human to approve high-impact actions before they are taken." Deciding what a project will and won't do is exactly that kind of high-impact call — it commits time, budget and people before a single task is scheduled.

A worked example: redesigning new-starter onboarding

A 40-person software company's operations lead gets a two-line ask from the CEO: "Onboarding takes too long and new hires seem lost for weeks. Fix it." Handed to an AI assistant as-is, that ask could produce almost any project.

The operations lead gives the assistant more: the CEO's message, plus her own knowledge that "too long" currently means new hires take about six weeks to reach full productivity, and that the CEO's real complaint, from three separate conversations, is that new hires don't know who to ask for help. She asks the assistant to draft a goal statement and a first-pass in/out scope list from that.

The assistant proposes a goal: "New hires reach full productivity within three weeks, and can name their go-to contact for any onboarding question by day two." It proposes scope: in — a written 30-day onboarding checklist, a named buddy assigned to every new hire, a single onboarding contact point; out — office relocation, benefits enrolment changes, hiring-process changes upstream of an accepted offer.

The operations lead does not treat this as finished. She checks the three-week figure against actual ramp-up data before agreeing to it, confirms with the CEO that "office relocation" really is out of scope (it is — a separate project already owns that), and adds one scope item the assistant had no way to know about: onboarding must stay inside the existing HR software, because a system change is already blocked this quarter. The goal and scope only become real once she — not the assistant — has confirmed them.

Accessibility notes

This lesson is text-first, with no images, audio, video or downloadable artifacts. The practice exercise's model answer sits behind a native disclosure control that is reachable and operable by keyboard and correctly announced by screen readers. The knowledge check uses native radio-button inputs with a visible question and options, and posts its result to a live status region so assistive technology announces the outcome without a page reload.

Sources and limits

This lesson synthesises the sources below into a practical learning model. It is not a security standard, legal advice or a guarantee that any particular agent design is safe.

1. Project management glossary — APM (Association for Project Management). Defines "objectives" as predetermined results towards which effort is directed, and "scope" as the totality of outputs, outcomes and benefits and the work required to produce them.
2. What is scope management? — APM (Association for Project Management). Explains that clearly defining what is in and out of scope prevents misunderstandings that lead to later issues and change requests.
3. AI Risk Management Framework 1.0 — NIST AI Resource Center. Frames an AI system as an engineered system that generates outputs such as predictions, recommendations or decisions — not a self-directing decision-maker.
4. LLM06:2025 Excessive Agency — OWASP Gen AI Security Project. Recommends human-in-the-loop control requiring a person to approve high-impact actions before an LLM-connected system takes them.