So I might arrive at 200, 450, 800 hours 20, 40, 80 days as my estimates and choose to use 460 hours and 42 days as my planning values. In other words, in your example above, you know that talent A is 50% and talent B is 50%. ![]() Instead, estimate using min, max, and most likely values for both work and duration with the assumptions of your talent at specific utilization levels. So worrying about ensuring your resources are not over- or under-allocated is kind of a waste. Third, your schedule will be perfectly "leveled" just at the time you punch your baseline it will be perfectly unleveled thereafter. So allowing MS Project to calculate this for you will very likely give you erroneous indications of duration. It will calculate it the exact same way no matter the work and, unfortunately, tasks have varying degrees of elasticity. Second, MSProject will calculate your duration off of work and resource availability assuming a perfect resource elasticity. So managing to duration seems more intuitive to me. ![]() My answer will not technically answer your question but may provide you with another alternative in building your schedule.įirst, I prefer to keep all / most of my work packages as fixed duration since in most cases we as PMs have to communicate a firm delivery date. I am going to answer this question in a completely different way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |