One issue I have always had with most software project tool is load balancing between planning and implementing stages. The issue we need to plan the type of skill level with load balancing to project expected levels and types staffing per roles needed. Said another way, we use staffing by categories to forecast staffing by role needed – so we can consider roles needed in combination with learning level requirements. Consider, the skill level within a defined role of a given person changes very significantly between six, twelve, eighteen, and 24 months but is fairly constant from 2 years to 5 years. Thus, if your resources are limited to people with less than 2 years more training and supervision will be required with the six months level requiring the most. This same grading of level of experience applies equal to company knowledge (acculturation effect) level of experience, another significant forecasting issue that can increase funding levels. And so-on and so-on .
However, when we assign an actual person, they may fill more than one of these forecasted roles and they are usually over loaded (how about 120 for a 40 hour work week). Obviously you can’t avoid this overload skewing. It can be mitigated as long as it does overly skew monthly, quarterly or yearly manhour planning. Once the initial planning with overall WBS has been iterated a couple of times a guesstimate of actually staffing levels can be used, But this doesn’t guarantee the actual persons wanted can be acquired so recasting using a scheme such as PA1, PA2, etc can be used to possibly reduce the eventual skewing of actual person/role versus manhours forecasting. Also, one would like the system to keep this staff forecasting by role for comparison against actual staffing. More fun stuff…
LinkedIn: The Project Manager Network – #1 Group for Project Managers
Topic: Any recommendations for a project management software?