Excluding Counts from Baseline Update

The Count Sessions for a Release can be selectively used to update the Production Baseline Release. If a change request for some reason was not implemented or you do not want the Count to reflect its outcome in the baseline then SCOPE will let you decided how you want it handled.

Situations when this may occur are when the Count Session was:

• Not approved and the project did not proceed, then the Count Session can be deleted and the integrity of the Release is retained.
• Not actually implemented but the project is still in progress or is planned to be implemented at some time in the future. In this case SCOPE allows you to selectively exclude that Count Session from the Update to Baseline i.e. puts the Count Session on Hold and SCOPE will create a new WIP Release, based on the new Baseline Count but also includes the 'Held Over' Count Session so that is now part of the Latest Release Count. It will be removed from the previous WIP Release where it was originally created.
• Conversion functionality or any functionality delivered by the project but not in the Production Release. SCOPE allows you to select to NOT Apply the Count Session to the particular Baseline Update. The Count Session will remain in the Work in Progress Release where it was created but its impacts will not be considered in the Update to Baseline.