Concourse Feedback
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.
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,
We have multiple complaints from the stakeholders related to delivery process organization management content in PDM. We mainly have 1 core deliverable as delivery playbook, project charter or ways of working document (different names from territory to territory). However, in PDM we have majority of those elements in multiple deliverables. There is a room of significant improvement of Delivery Process organizaiton into 1 core deliverable that will cover such tasks as set-up project governance, select and set-up project tools, document ways of working, RACI, comms approach, stakeholders assessment, RAID and CR processes, etc. Moreover, this document should be maintained and updated through entire delivery based on internal and external retrospectives to ensure that we are properly collecting and addressing to maintain project quality. Happy to provide more information during refinement sessions.
| Workspace Territory | N/A |
| Platform & Practice | CSX - CSX powered by Salesforce |
| Technology | Salesforce |
I believe this topic should evolve into something different. Previously we had a focus where we were creating content for PDM and making content pre-selection for offerings and adding assets after. Now, we have situation when users are doing PDM review they are thinking from deliverables perspective and what are they usually creating in the project: we can call it asset focused delivery. So technically, assets are defining content not vise versa. So, in some situation we have one big asset deliverable that covers multiple PMD content elements [meaning L4]. Also, we have recent complaints that there are a lot of duplicates in assets and we need to have some universall templates [e.g. CSX or PDM based] to avoid creating similar assets where we can re-use and upgrade existing ones. Moreover, there are a lot of old branded assets or super outdated elements that requires massive rework before they can be used.
Thank you for your submission. We have received and will be evaluated your request. The Idea status has changed to in Review and we will contact you with a response.
Thank you for your submission, this has been routed to the PDM Content team to review and provide an update.