Ongoing Activities Crashing PDM Plan - alternative proposal

Hi Team,

Based on our recent observations and feedback from recent pilots [e.g. ASFC project from CA], we would like to highlight issue about some type of deliverables and events [primary related to project governance and project quality management].

Current flow: we have activities, deliverables, events that are related to ongoing project governance (e.g. per sub-stage), however, due to nature of those activities some elements cannot be closed as activity will last until end of stage/sub-stage or even project.

Impact: project teams cannot create proper high level plan as relation child to parent causing due dates extensions for sub-stage / stage due to the opened ongoing activities.

Proposed flow: to split set-up of project governance / ways of working [and similar items] and ongoing management and move second part to separate place [new stage or even different approach] to avoid having ongoing child activities under core PDM stages/sub-stages.

Impact: high level plan will have more sense and will be easier to manage. Moreover, ongoing management context is currently moved out from core project structure [by deletion, withdraw or moving out from the structure].

From some projects we know that ongoing reporting or milestones tracking is often created by dedicated issue types [similar to RAID+CR].

Without this change Using PDM Structure for planning is complex and requires too advanced Jira skills, PDM knowledge and high level customization.