Typical usage

The following information is based on typical usage of PPM and Project Management. It is not warranted that you will have the same or similar experience.

Table A-1. Project Management Typical Usage lists entities with an amount for its typical usage, comments about typical usage, amounts that are considered complex and might impact performance, where that performance impact might occur, and recommendations or comments about complex usage.

Table A-1. Project Management Typical Usage

	Typical	Complex	Performance Impact	Recommendations/Comments
Number of Tasks	50–500	> 5,000	Load work plan, cost roll-ups	Do not create a task that represents a generic topic such as vacation or training. Shorten the project duration and simplify work breakdown.
Number of Levels in a Work Plan	< 5–7
Number of Resources Assigned to a Single Task	< 100a	>= 50	Time sheet submission, cost roll-ups	Performance depends on the number of resources per project rather than the number of resources per task.
Number of Resources Assigned to an Entire Project		hundreds		Make tasks more granular to optimize performance for resources entering time and for project managers and summary task owners.
Duration of a Single Leaf Task	<= 1 year			Model large projects with a separate project for each phase, with each phase lasting three to five years.
Duration of a Single Summary Task	< 5 yearsb	> 2 years	View work plan, enter time on a time sheet or task, approve time
Duration of a Project			Cost roll-ups	Accumulation of time sheets increases work load for services and resource utilization calculations.
Number of Time Sheets Logged Against a Single Task		thousands		Performance depends on the number of resources assigned to the task and the task duration.
a.    For tasks with a duration of less than five years.     b.    For tasks with less than 100 resources.