[for the discussion] PDM simplification proposal - Remove L3 as level from PDM

Hi Team,

As a part of recent content changes coming from Delivery Standards, we have raised this request previously. https://concourse.ideas.aha.io/ideas/CONC-I-2399 [that ticket can be closed, but it can be treated as root cause of this request]/

Based on recent check with pilot teams [majority of territories with whom we are working], L3 is quite confusing for the users as they are not using at the project delivery [it provides some kind of group (if we do not have relation 1:1 between L3 & L4), but is not used for the delivery, and even creates technical issues. Let's me explain on the example below:

1. We are in the first phase of the project: L1 Align, L2 Plan.

2. As a project manager I would like to create a Kanban board to plan my L4 delivery with the team. However, I cannot create it as above L4 we have L3 that is limiting us create Kanban board in the format: all L4s from selected L2 sub-stage.

3. Moreover, we are not targeting to create any reporting on L3.

Technically speaking L3s lost its purpose and just only creates complications in overall project management.

Additional arguments to against L3:

1. No (or min) assets linked to them

2. Scoping is always done vs deliverables, not vs activities.

3. Technically we should have deliverables higher in the structure: as to do something for the client [client deliverable] we need to do some activities [but we have already task and sub-task] so ... activities should not be higher and technically not needed.

4. Moreover, for ongoing work we can use events [L4] instead of activities.

There are some potential cases where we have L3 but not L4 under them. So technically we need to check if those mainly "ongoing activities" should not managed differently. Happy to discuss this topic.

Kind regards

Olek