What are the Project 'Execution Type' implications?

CGS92
Mega Contributor

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. 

1 ACCEPTED SOLUTION

Uncle Rob
Kilo Patron

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.

View solution in original post

18 REPLIES 18

Hi Matt,

Thanks for checking and responding... Trust you are linking it..

Let the feedback flow in, it helps.

 

 

find_real_file.png

 

 

Just discovered this Field as I am evaluating ITBM Portfolio Project Management using Demand Management.
When a project is created with Create New from the menu, it will show a form where the Execution Type can be set. However when a project is created from a Demand (which happens in the background), there is no way to set the execution type, it defaults to Waterfall. As a stop gap measure I added the Execution Type as a field on the Default Form for Project, so PMs have the opportunity to set the value to their liking and therefor control the related lists shown.

Hi Peter,

Thanks for sharing this point. After creating a project from demand, PM can still change the execution type from the Details tab (of the project). However since the field is not visible on the default (project) form, it is not intuitive.

Most of the times project manager & project execution type are known while creating the project from the demand that is why I am planning to add the project execution type from Demand -> Details tab. Value set in this field will drive the execution type of the created project. If required, PM can still change the execution type after creating the project (from Project -> Details -> Execution type).

Thoughts?

Thanks,

Namita Mishra

Hi Namita,

After I wrote the reply I saw that execution type is indeed on Details tab of Projects. Personally I feel it is a core attribute of a project and should not be tucked away in Details. So I added it right under Status.

In our case the project type may often not yet be determined when the demand is approved, but it would make sense to add this field to demand and have it transferred when the project is created. I guess it is a matter of educating PMs they can change the type at will to show/hide the appropriate related lists.

Thanks, Peter

Hi Peter, I agree with the point that it is more of a point of educating the PMs. Thanks, Namita Mishra