R
Rich Eaton
As many will be doing some 2005 planning soon, it is often helpful to
have an initial plan as to what projects we can absorb in the next
year, and how many resources it might take, and what would happen to
next years project capacity if we added resource, lost resources or
applied them differently. There's a lot written about the potential
for using Project Server to do resource capacity planning. It's
obvious how that can work for projects that are already underway using
Portfolio Analyzer and other views. For projects that are still in
the not-started, conceptual stage, it would seem that you could load a
shell project that had some basic phases and generic resource
assumptions. Is that approach working for anybody? What has and has
not worked for you? Is there a good way to assign generic resources
in a way that you can quickly vary them to see the impact of
adding/taking away resources?
have an initial plan as to what projects we can absorb in the next
year, and how many resources it might take, and what would happen to
next years project capacity if we added resource, lost resources or
applied them differently. There's a lot written about the potential
for using Project Server to do resource capacity planning. It's
obvious how that can work for projects that are already underway using
Portfolio Analyzer and other views. For projects that are still in
the not-started, conceptual stage, it would seem that you could load a
shell project that had some basic phases and generic resource
assumptions. Is that approach working for anybody? What has and has
not worked for you? Is there a good way to assign generic resources
in a way that you can quickly vary them to see the impact of
adding/taking away resources?