To create an In or Out of Scope List
Description
The Goal of the In and Out of Scope List is to define the boundaries of the project during Start-Up it will be updated and reviewed during each stage.
Preconditions
You have created a Discovery Mindmap
Postconditions
You have created an In or Out of Scope List suitable for use when creating a Business Deliverable Breakdown
Actors
Project Manager
Trigger
The availability of the project brainstorm mind-map
Main Success Scenario
- The PMs organise the raw mind-map data
- save a working copy with in the format <original file name>-organised<suffix>
- de-duplicate, edit and organise the raw material. (This will typically reduce the number of items by 40% and make it much
more readable) - work the new mind-map by adding your own structures and items, typical content will include
- possible deliverables
- risks
- issues
- resources – men, materials, money
- The PMs create the In or Out of Scope List (template) by identifying potential deliverables and exclusions
- Higher level nodes in the Mindmap will tend to be categories in the In or Out of Scope List
- Lower level nodes in the Mindmap will tend to be items in the In or Out of Scope List
- They apply skill and judgement to decide if the item is In or Out of scope
- Repeat this for all mind-map items until you have created a first In or Out of Scope List
- Review each Category in the In or Out of Scope List. There should be a few of each “In”, “Out” and “?”. If there are insufficient “Out” and “?” brainstorm until you have some more. These are necessary to define the boundaries of the project
- Each line should be updated with the stage at which it entered or left scope. This is to aid understanding of schedule changes
caused by changes in scope. - Create a PDF of the In or Out of Scope List
- Discuss this first draft of the In or Out of Scope List with the Project Executive. This draft will be updated during the SU Planning
sub-stage - Update the risk and issue logs
- The Goal is complete