Page History

Escalation rules apply to this process.

• Three days after the Start step the e-B admin is notified.
  • If a PM has been identified, the e-B Admin will put that person in the role and add a note to the PM that the TA process has been in the “Team Assignment” step for 3 days but is still incomplete.
  • If the PM has not yet been assigned, the eB Admin will send an Action Item to the Program Manager requesting that the PM be assigned. Once the Action Item response is received, the PM will be put in the role and a note added to the PM that TA process has been in the “Team Assignment” step for 3 days but is still incomplete.
• Seven days after the Start step the eB admin is notified.
  • The eB Admin will move the process to the next step, putting only identified team members in roles (and notifying them).
  • If additional team members are required, process "01.03-Add a Resource to a Project" should be used.

The process is usually started by a Spawn step, but can be started by the eB Admin or Project Manager.

In this step a Program Manager. Project Manager and CC Planner can be assigned. The Program Manager is required.

When complete the Submit action is taken.

1. If a Project Manager assignment has not been assigned the process moves to Team Assignments - Including PM.
2. If a Project Manager has been assigned the process moves to Team Assignments - PM previously assigned.

Each assignor in this step assigns their respective team members and takes the Submit action.

Note that some roles are required before the process moves forward.

The next step is eB Admin.

Each assignor in this step assigns their respective team members and takes the Submit action. Note that Project Manager is a required field for this step.

The next step is eB Admin

An eB Admin reviews the assignments and automation assigns all team members selected to the project front end and backend at the project role level and completes the process.

The next step is Finish.