Project scope
The agreed boundary of the outcomes and work a project is intended to include.
What is project scope?
Project scope describes agreed outcomes and the work involved in producing them. It also records which services are initially excluded. Assumptions, interfaces and required contributions help make this boundary understandable. A list of screen names alone often leaves unclear which task should actually be solved completely.
In a fictional project, the initial solution includes submitting a service request and the team processing it. Automatic invoicing is explicitly excluded. If it becomes necessary later, benefit, effort and effects on the existing plan are assessed. This means neither that every change is forbidden nor that it is automatically included. Participants must record the new boundary and the associated decision traceably.
Sources
Related terms
- Change requestA change request records a proposed change to an agreed project baseline for assessment and decision.
- Statement of workA statement of work explains the requested scope: outcomes, boundaries, contributions and prerequisites. It helps put quotes on the same basis.
- Product discoveryInvestigating needs, constraints and risky assumptions before settling on a product solution.
- Product OwnerThe person accountable in Scrum for product value, the Product Goal and effective backlog management.
- Definition of DoneThe shared description of the quality conditions a completed product Increment must meet.
- User storyA short description of a user role, a need and the goal behind it.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.