Concourse & Jira Cloud Portal
with the updates from delivery standards to new content, 1 to 1 relationship of L3 to L4 is confusing and makes the flow of PDM too granular, we would like to go back to 1-to-many relationship typically seen in most hierarchies.
We have reviewed new changes from deliverys standards with our stakeholders and 1 to 1 relationships between L3 and L4 causing a lot of confusion, additional work to be done to manage additional L3 and not in line with multi times previously raised feedback about too many items in PDM and simplification needed and we are moving into opposite direction.
Hi Team,
I propose to merge another issue to this one https://concourse.ideas.aha.io/ideas/CONC-I-2429. This one to keep as main.
Core suggestion based on discussion with our stakeholders based on recent pilots:
PDM Structure [even for simplified Salesforce program] is too complex and contains to many levels and items
Core logic is to plan deliverables under concrete stage and sub-stage and only after all activities, tasks and sub-tasks to produce those deliverables.
Additional feedback, that we have received is that for Salesforce project our core deliverables are dependent on business capabilities that to be covered by technology. For those business capabilities we can have current deliverables [business design, functional design, tech design, build/config, unit testing, SIT, UAT, etc.]
Based on discussion with some territories during the pilots and during solution presentation, users raised the opinion that L3 in total is not needed. Technically our focus should be:
Stage -> Sub -> Deliverables -> Tasks & Sub-tasks need to complete those deliverables.
Activity is not used during work planning in Jira and just makes overall amount of items almost doubled [as we have mainly 1-1 relation between L3 and L4]. We need to reduce complexity and amount of work items.
Hello Olek, apologies for the delay on this, I have escalated to our Content team for their review and feedback.