Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
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
Oleksandr Prokopiv
Hi Team,
Additional observations from current intelligent scoping approach:
Users very often receive different recommendations with the same input [tested multiple times during the training and parallel scoping].
In some cases [e.g. lack of precise mentioned about technology], IS cannot provide "CORE"=main offering that also confuses the user.
Finally, IS provides too many outputs and does not try to minimize scope elements. Instead it does not tries to cover deliverables, but propose all options where some those deliverables exist [e.g. if some future state architecture are in place in SOW, IS provides all offerings and DS where this elements matches, but not the best one that covers other deliverables as well].
Hey Olek, thank you for your submission. We are currently evaluating improvements to Intelligent Scoping and will utilize this to help influence the plan.
also, if some items are not existing in PDM they should be highlighted to the user and suggest to create them directly in Jira or to add them in Concourse as project specific L4 [we have another Aha for it].