Scope
1 area implies 6 topics across 2 modules
You did not pick these
Supply Chain Management
Your streams cross into this module, so the work happens there too. That is the part most scoping exercises miss.
The end-to-end
Lead-to-Order
Customer Relationship Management
- 01Contact-to-Leadimplied
- 02Lead-to-Opportunityimplied
- 03Opportunity-to-Quoteimplied
- 04Quote-to-Order
Data in and out
What actually crosses the boundary, which way, how often, and what it costs when it stops.
Crosses your scope boundary
Customer orders←Sales Force Automation
Continuous
Order Processing \u00b7 without it: Orders are rekeyed and differ from what was agreed.
Integration points
Every module boundary a stream crosses is an interface. The ones marked straddle your scope — you are changing one side and not the other, which is the interface most often missed at scoping and found during testing.
Customer Relationship Management→Supply Chain Management
Quote-to-Order
One side of this is outside your scope
Concerns raised
Australian obligations in scope
Nothing AU-specific in this scope.
Everything in scope — 6 topics, 5 you did not pick
Next
This is a diagnosis, not a plan
Build takes the same scope and turns it into the documents somebody has to write — the investment brief, the business case, the plans — starting with what each one needs as an input before its headings can be answered honestly.
Build it →Share this scope
The scope is in the address bar. Send the link and the other person sees the same picture.