Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Put Simply: Users input counts of item types, with inputs grouped by complexity level (low, medium, high and in future N level).
Acceptance Criteria:
Complexity Matrix step follows the Work Item page
If it is not necessary to define the complexity of any work item in scope, user bypasses the complexity matrix step.
Users will see all relevant complexity matrix item types (ex. Reports, Workflows, Interfaces) based on their scoped offerings
Default item counts are pre-populated with values designated in admin configuration.
For each item type, users can edit the count per complexity level.
For example, when entering the quantity of Reports at each complexity level, a user can input 20 low complexity reports, 10 medium complexity reports, and 4 high complexity reports-- then proceeds to input the number of low/medium/high complexity Workflows.
A total is auto-calculated per row (item type), based on the sum of inputs.
These inputted numbers (ex. 20, 10, 4) are then multiplied by the (baseline or accelerated?) effort values set up in admin config (ex. *12, *40, *56)
Ideas for Future:
Show which scoped work items map to each complexity matrix item type, improving transparency and accountability.
Visually distinguish between default values and user-edited inputs
Provide a breakdown of the calculation logic (Inputs × Configured Effort Values) so users can understand how effort is derived for each item type - consider a visual explanation as well
Introduce smart defaults or recommendations based on prior estimates (e.g., "Use recommended complexity mix based on NNN similar past estimates").
Carly Hu
