Intelligent Scoping - Logic change

Hi Team,

Currently feature of intelligent scoping has one major cons for usage: it provides too many results and force user to review all results [offerings and delivery standards] before having final scope.

Proposed logic change based on the example: we have Salesforce Service Cloud related project with end user training and without UAT Testing on PwC side.

Based on contract [SOW or other document] once uploaded Intelligent scoping should provide:

• Core offering that matches to the provided document and provide % of elements and recommendations what should be removed. In this example the scope should be around 85% because:

  • We are not doing UAT testing for the project - Intelligent scope should highlight to remove those lines from the delivery plan [nice to have list of L4s to be moved out or even removed by the agent]

  • Also, we have some additional content from Training Delivery Standard that should be added [Agent should add that Delivery Standard to the scope with selected deliverable needed for this particular engagement].

In such situation, user should directly go and check final delivery plan based on AI analysis and assumptions.

It will be nice help to the project team as they do not know and technically will never know whole content inside PDM and we need to have the possibility to narrow down the outputs to what they really need.

Kind regards

Olek