How does percent_complete increment on Project form?

[MBarrott]

I want the percent_complete field to increment if ANY closed state is selected. Right now it only increments if the Closed Complete is selected for a respective project task, ignoring Closed Incomplete and Closed Skipped. 

I think it is a business rule but I couldn't see anywhere to adjust the valid state values to accommodate this change. 

[Dhiren Aghera]

These was helpful @Namita Mishra  

On thing that I wanted to check is if I have few tasks in my project plan which has been marked Closed Incomplete or Closed skipped after some % progress and if all remaining tasks are closed complete what happens to the overall Status and % complete.

In my PDI in the classic planning console the Overall state moved to Closed Complete but the percent complete was not 100%. However in the New Project Workspace it was showing Closed complete and 100% which I think is the right behavior.

The planning console and new project workspace is not getting synced properly.

Do you observe the same.

[Namita Mishra]

Hi @Dhiren Aghera ,

Hope you are doing well.

This is how it is designed:

1. All the tasks are closed as Closed Incomplete - Project state will be Closed Incomplete

2. All the tasks are closed as Closed Skipped - Project state will be Closed Skipped

3. At least one task is closed as Closed Complete - Project state will be Closed Complete

4. Project is closed as Closed Skipped, then all the pending / open / WIP tasks will be closed with the state as Closed Skipped [No impact on the already closed tasks with Closed Complete state]

5. Project is closed as Closed Incomplete, then all the pending / open / WIP tasks will be closed with the state as ClosedIncomplete [No impact on the already closed tasks with Closed Complete state]

Point #1:  If few tasks in my project plan which has been marked Closed Incomplete or Closed skipped after some % progress and if all remaining tasks are closed complete what happens to the overall Status and % complete.

=>I think you meant overall state i.e. project state.

    In this case, Project state will be Closed Complete.

    Suppose there are 3 tasks and every task is of 1 day.

    Task 1 = 100% ; state = closed complete

    Task 2 = 50% ; state = closed incomplete

    Task 3 = 50% ; state = closed skipped

In this case project state = Closed Complete and %complete = 66.67%

Point #2: In the classic planning console the Overall state moved to Closed Complete but the percent complete was not 100%. However in the New Project Workspace it was showing Closed complete and 100% which I think is the right behavior.

=> In this case planning console as well as New Project Workspace (NPW) should show the same behaviour, similar to shared above.

I have tested this point and getting the same behaviour in both the UIs as expected.

Please refer below screenshots:

Legacy Planing Console:

NPW:

 

Hope this answers the points. If it does, please mark it as correct answer.

Happy SPM Journey !!

Namita Mishra

[Dhiren Aghera]

@Namita Mishra  thanks for your response and I am aligned now. The only thing that still I feel need to be thought about is the scenario where because of few tasks in close skipped or closed incomplete state the overall project is not showing 100% complete even after all remaining tasks are 100% closed complete. I feel the overall project completion should reflect 100% once all the tasks are marked as either closed complete, skipped or incomplete no matter the % complete of the tasks

[Namita Mishra]

Hi @Dhiren Aghera ,

Thanks for the response...

I think you are also correct.. It is different ways in which our customers respond...

Just to share the thought behind this design (not trying to prove this is the only way):

1. Based on the users interviews, it was very clear they want to see if all the tasks were completed or

      some of them were decided not to proceed because the requirement / ask changed mid - way hence it was closed as Closed incomplete.

     whereas some were created but did not even got started because the requirement was misunderstood or even before planned start date, the ask was updated... so rather than deleting the task it was kept for future reference but closed as closed - skipped

2) Now, in either of the cases - (Closed - Incomplete or Closed -Skipped) - the percent complete of the task may not be 100%. In this case if the project is shown as 100% then PM has to refer the tasks of every project to find out if any of them was Closed -Incomplete or Closed - Skipped.

Also, another reason was that the percent complete always rolls up and if we mark the project as 100% then users have to remember two calculations - if all tasks are Closed - Complete then project %complete = roll up of all the underlying Tasks' percent complete otherwise ignore the tasks' percent complete and still mark the project as 100% - This might have become very difficult for the user base...

Just shared all the reasons behind this design - Main idea was:

1. To keep it simple. Do not tweak OOTB calculation

2. Let the PM know just by looking at project %complete whether all tasks are Closed - Complete.

Hope this helps.

Thank you!

Namita Mishra

[Dhiren Aghera]

@Namita Mishra  thanks for the explanation and as said I think its completely driven by customer view point and it is never the same.