The scope of a project is usually approached from a two-dimensional viewpoint – in and out, within and beyond, what will be done and we will not.
And is often closely followed by a shallow caveat that says something along the lines of – ‘Anything that is not explicitly stated as in scope is considered out of scope.’
But for this statement to hold water, the potential for everything must be explicitly considered.
Brands, divisions, roles, processes, functions, applications, integrations, activities, deliverables, migrations, and the list goes on…
Business, system and project are good lenses to look through when defining scope.
One should only ever dive into the deep.