What are the Project 'Execution Type' implications?

[CGS92]

Dear Community Member, 

On the Details tab of the project form there is the field of 'Execution type' which can be set to Waterfall/Agile/Hybrid. After some research on the multiple types it remains unclear what the implications are of this field and its selected value. On first sight there aren't any differences between Agile/Waterfall/Hybrid in the;

- Project form view

-Related list/links

-Planning console

-Project Workbench

Furthermore, I am unable to find any business rules related to this field. Also the docs don't provide any concrete answers. 

Is anyone familiar with the implications of this field and its values when selected? If so could you please elaborate on them.

Thank you. 

[Stephen Sturde]

Hi CGS92 -

I've recently been working on a project that addressed this very thing. There is nothing driven by this field. Our team made a couple adjustments so that we could use this logically.

1. Added phases to the phase field choice list, and made the phase field dependent upon the Execution type. This way each type could have it's own phase set. Note that due to a system limitation, we could not create a different Process Flow across the top per execution type. There is only 1 process flow per table.
2. Added new views and view rules. Each Execution Type has its own view with its own field set and related list set. This gave a more tailored experience to the project teams. 

[Uncle Rob · Accepted solution]

No mechanical implications.  Its strictly an informational field.
You could, without consequence, pack agile phases into the project and still select "Waterfall".

Its just a currently non-automated way for companies that use all 3 of those methodologies to understand what projects are using them without doing more complex queries.

[Rajesh_Singh]

'Execution type'  - Purely informational field. It drives nothing. No automation done for this feild until Madrid. As Robert said, this is just informational for one to understand what type of methodoloy one is using for this project. 

[Matt Hernandez]

It is however on the form, and breakdowns are provided for it on the new PMO Dashboard indicators. I was going to hide that field since I didn't think our PMO had clearly defined when to use those choices, but then I went to PMO Dashboard in my Madrid testing instance and clicked on some graphs, then selected the Execution Type breakdown/filter and was surprised to see a lot of 'hybrid' projects. Some important folks have set their projects to 'hybrid' so I figured they may wish to breakdown that way on the dashboard. So I'm leaving that field alone.