Each task in MSP follows a scheduling mode:
- Auto Scheduled MSP calculates start/end dates based on dependencies, constraints, and calendars.
- Manually Scheduled User controls dates; MSP gives flexibility.
These modes act like “profiles” controlling how strictly the scheduler behaves.
Constraints define how a task can be scheduled:
- As Soon As Possible (ASAP)
- As Late As Possible (ALAP)
- Must Start On / Finish On
- Start No Earlier Than, etc.
These act like job rules applied to tasks.
Calendars define working/non-working time:
- Project Calendar
- Resource Calendar
- Task Calendar
Examples:
- Standard 9–5 schedule
- Night shift
- 24-hour operations
These effectively behave like scheduling “profiles” for when work can happen.
Resources influence scheduling through:
- Availability (units, working time)
- Max capacity
- Cost rates
For example:
A full-time engineer vs part-time consultant
- different scheduling outcomes.
Resource leveling settings act like execution profiles:
- Priority (0–1000)
- Leveling order (ID, standard, priority)
- Automatic vs manual leveling
These determine how conflicts are resolved when resources are overallocated.
In Project Server / Project Online, admins can define broader scheduling behavior:
- Default scheduling mode
- Timesheet policies
- Task update rules
- Resource engagement settings
These are closest to true “job profiles” in enterprise setups.
If you need actual “job profiles,” organizations often simulate them using:
- Templates (e.g., Agile vs Waterfall project templates)
- Custom fields (tagging tasks/resources)
- Macros or VBA automation
- Different calendars + constraint presets
A “Development Job Profile” might include:
- Auto Scheduled tasks
- Standard calendar (Mon–Fri)
- ASAP constraint
- High priority
- Assigned to full-time resources
A “Maintenance Profile” might use:
- Night shift calendar
- Flexible/manual scheduling
- Lower priority
