Concourse & Jira DC Portal

Put Simply:

Instead of manually completing multiple estimation steps in the Concourse UI (drivers, complexity, staffing, etc), engagement teams will use a structured Excel template with tabs for each of the input fields. This approach condenses the multi-page ePro legacy experience into one consolidated input method.

Purpose:

This exploration is intended to evaluate technical feasibility, as well as UX tradeoffs — to determine if teams prefer a single, editable artifact over guided UI steps. We will need to partner closely with the tech team to determine which implementation options are possible, whether this approach aligns with platform constraints, and assess the timelines of each of the potential flows.

High-Level Acceptance Criteria:

• Proposed user flow (3 options):

  1. Embedded workbook:

     1. Excel table is embedded directly after scoping in the estimation section of CC, allowing users to edit cells (and thus Estimation inputs) within an Excel table in Concourse.

     2. May reduce context-switching and enable validation during entry.

  2. Save It auto-generated workspace file:

     1. Concourse auto-generates an estimation Excel file and drops it into the team’s Save It workspace.

        1. Allows the team to collaborate offline on best inputs for Drivers/Complexity

     2. Team collaborates within Save It, then either uploads back or automatically syncs with Concourse for estimation.

  3. Download + upload:

     1. User clicks "Download for Estimation" from the scoped Delivery Plan page.

     2. A structured Excel file is downloaded and/or saved directly to the user's Save It SharePoint workspace.

        1. Could be to the User's local download as well

     3. User fills in estimation details and uploads the completed file.

• Excel Template:

  • Pre-populated list of work items based on scoped Delivery Plan

  • Inputs for:

    • Work item-level PwC/Client/Vendor split and accelerator selections

    • Complexity matrix inputs

    • Driver selections and driver input values

    • Team structure

    • do we need for Project Size

• Estimation selections can be completed entirely via Excel input.

• Users must upload or confirm a valid Excel file to proceed to estimate summary.

• Excel-based entry remains part of the overall scoping flow.

Open Questions & Considerations (dependent on User Flow):

• Validation & error-handling: Does validation occur upon upload or within the excel file?

  • What types of error handling will we need (missing inputs on Excel sheet, whitepage errors, etc)

• Collaboration: How do teams coordinate input to avoid overwriting each other's changes?

• Editing & rework process: How are edits tracked and reconciled (especially across versions)?

• Multi-Model estimates: How are multiple estimation models handled — separate workbooks, tabs, or tagged entries?

• Calculation logic: How do we avoid embedding logic in Excel while still triggering calculations in the admin-side while the user inputs information?

Low-Fidelity Mockups