Answer.

The project scope is a clear definition of what needs to be implemented within the project and what is excluded from it. Proper scope definition provides an understanding of the workload, prevents "scope creep", and allows for effective control over resources and timelines.

The business analyst describes the scope using:

Stakeholder maps.
Context, boundary, and interface diagrams.
A function catalog in the format of user stories or use cases.
An "out of scope" manifesto (exclusions).

Key features:

The project boundaries are fixed before detailed requirements are elaborated.
They serve as a benchmark for approving any changes.
They establish a real measurable volume of commitments for the team.

Tricky Questions.

Is it sufficient to define only the main functionality to consider the scope fixed?

No. It is necessary to explicitly state what is NOT included in the project to avoid double interpretations and "hidden" expectations.

Does the business analyst have the right to unilaterally expand the scope if they consider it useful?

No. Any change in scope is agreed upon with clients/stakeholders and is usually formalized through a change request procedure.

Can the project boundaries be changed after they have been agreed upon?

Yes, but only through a formal change management process, with a review of plans, cost estimates, timelines, and the agreement of all key stakeholders.

Typical Mistakes and Anti-Patterns

Lack of clear demarcation between what is included/excluded in the project.
Adding new tasks without considering their impact on timelines and budgets.
Agreeing on scope only verbally, without documentation.

Example from Life

Negative Case

The scope is defined verbally, without a clear document. During the process, additional tasks arise that the stakeholders "expected".

Pros:

Flexibility, the ability to adapt to new tasks.

Cons:

The project exceeds timelines and budget, leading to misunderstandings between the team and the client.

Positive Case

The analyst documents the scope, agrees on exclusions, and any changes go through the change request system.