You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love this tool, thank you@countincognito!! (I signed up to sponsor, because now that you're making project tracking so fantastic I won't need Microsoft Project anymore. 😁🎉)
For my projects, I typically need to calculate a project cost estimate using billing rates, which will vary by resource. However, efficiency in particular should be based on effort, not on money spent (for example, an architect costs more than a tester, but that shouldn't impact efficiency). In addition, some resources need to be assigned only part-time. I think the following behavior could work:
"Unit Cost" is used as the 'effort weight' input for a resource. That's true now; it might help to just rename the column to 'Effort Weight'. If I put 0.5 here, it means that that resource is treated as part-time; this can help, for example, if a project manager is part-time, to calibrate their impact on the project efficiency more accurately.
A 'Daily Cost' column is added for resources that represents the "$ per day" cost (i.e., the billing rate).
The 'Metrics' panel is updated to add "Direct Cost (¤):", "Indirect Cost (¤):", etc. which factors in the billing rate for resources
The 'Resource Settings' panel (or a new view like "Costs") shows all resources that are used for the project, and the total cost for each.
While I admittedly have some unique needs as a consultant that don't apply to internal projects, the items above feel like they would be universally applicable to any project in any organization.
The text was updated successfully, but these errors were encountered:
I love this tool, thank you @countincognito!! (I signed up to sponsor, because now that you're making project tracking so fantastic I won't need Microsoft Project anymore. 😁🎉)
For my projects, I typically need to calculate a project cost estimate using billing rates, which will vary by resource. However, efficiency in particular should be based on effort, not on money spent (for example, an architect costs more than a tester, but that shouldn't impact efficiency). In addition, some resources need to be assigned only part-time. I think the following behavior could work:
0.5
here, it means that that resource is treated as part-time; this can help, for example, if a project manager is part-time, to calibrate their impact on the project efficiency more accurately.While I admittedly have some unique needs as a consultant that don't apply to internal projects, the items above feel like they would be universally applicable to any project in any organization.
The text was updated successfully, but these errors were encountered: