Just to be clear, the "dynamically calculated completion percentage" referenced below is the progress bar that you see whenever you have a partially completed project. You can also see that bar next to the label "complete" in the project section of the task properties pane; also, to be super-clear, a numerical completion percentage is shown to the right of the bar in the project section.

This bar is showing what percent complete the project is. So, if a project consists of ten items and three remain uncompleted, you will see a completion percentage of 70. But this assumes that all tasks are weighted the same. If one of your completed tasks requires much more effort that the others, and that task is complete, you would like to see your completion percentage higher than 70.

Let's walk through how this works. Create a project named "project" and then create a subtask named "subtask". Mark the subtask complete and look at the completion bar for Project. It shows 50% complete. That is because there are two items, Project and Subtask, and one of them, Subtask is complete. So one complete out of two total is 50%.

Now, look in the task properties for Project at the Effort. It should show the default, which is 50. Now look at Effort for Suntask. It should also be 50. Change the effort for subtask to 75 and you should see the completion percentage change to 60. That's because one task has effort of 50 and the other has effort of 75 for a total of 125, so your completion is 75 out of 125 or 60%.

To use this as accurately as possible, set the effort for your largest task to 100 and set each other task (including the Project) to a number representing the task's effort as a fraction of the biggest task's effort. For example, if your biggest task will take 8 hours and your smallest task will take 2 hours, set the largest task's effort to 100 and your smallest task's effort to 25 because 2 hours is 25% of 8 hours. If you do not want the project entry to count as any effort, go ahead and set it to zero.

-Dwight

On 1/12/2018 11:52 AM, Christoph Zwerschke wrote:
Am 12.01.2018 um 17:35 schrieb robisme (Olivier R):
> Actually, there is a "energy" field, but it's named "effort". Rather usefull indeed.

You can certainly use it to describe the energy level.

But actually it's intended use in MLO is for something different - according to the docs it "affects the dynamically calculated completion percentage for a project" and "is different from time required for a task parameter. For example if you just read a book, it would require less effort than if you write MLO help documentation :-). It might take you the same amount of the time to accomplish these tasks but the Effort would be different."

In that regard it should have better been named "effect", "outcome" or "impact", because the effort is not always proportional to the outcome (this is the famous Pareto principle).

-- Christoph


--
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mylifeorganized/15cc9d40-053e-6937-3955-d270314517ed%40dwightarthur.us.
For more options, visit https://groups.google.com/d/optout.

Reply via email to