Concourse & Jira DC Portal

Put Simply Statement:
Admins can define custom calculation logic to determine driver impacts. This is the largest POC potential outside of Excel inputs. This would be the single largest innovation to Estimation since its inception.

Why it Matters:
Unlocks flexibility for unique project needs and ensures that estimation logic can evolve with business requirements.

What’s Needed:

• Admin UI for defining and testing calculation logic.

• Engine to apply custom logic in real time.

• Validation and error handling for custom formulas.

  • Simulation to validate that calculations are providing the desired result

    • Think it would likely be Effort

• Early ACs:

  • Admins can create/edit calculation rules for drivers.

    • Would be able to create a Driver, have it be assignable to work items as it is today

  • A 'text editor' is used to store calculation logic (maybe in python or another supported language)

  • An AI Agent is available via natural language chat to assist the Admin user in modifying the calculation logic

    • I.e. "Please create a driver that multiplies effort of the work item by the number of weeks in the Estimate and then divides that number by the number of teams in the project such as "(work item*number of weeks)/number of teams"

  • An AI Agent is capable of scenario planning and testing modified calculations to show changes from the current calculation logic

    • need exact explanation about impact on hours, and in various other scenarios

  • Custom logic is applied instantly in estimation screens.

  • Validation ensures no formula breaks the workflow.