Concourse & Jira DC Portal

Put Simply Statement:
End users can choose from pre-defined staffing models (Team Structures) to simplify effort allocation

Admins will have the ability to define multiple (N?) pre defined team structures that encompass the different teams involved in delivering, the roles in each team (staff level) and the roll on and roll off timelines for each of these teams. They can do this for both domestic and AC Teams

Why it Matters:
Determines resource allocation across the timeline of the project which significantly impacts resource timing and planning
Adding Team Structures for End User inputs allows them to Estimate with more flexibility and closer align to what will become the Flex Budget

It allows Admins to configure the most common team structures that their practice uses for quick shifting of role allocations to closer align to what will become the flex budget

What’s Needed:

• Admin UI for defining staffing models.

  • requires all role types, selection for domestic vs AC, roll on and roll off structures, hourly vs even spread hours staffing, etc

    • further enhancements have been requested by the team but are not in current day ePro

• User UI for selecting a team structure during estimation.

• Early ACs:

  • Admins create, edit, and retire staffing mixes and structures

    • ability to create up to N levels of structures and N max resources per team

  • Users select team structures and see impact on estimates.

  • Changes to team structure are reflected immediately in user side effort calculations.