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 move directly from scoping into estimation within the same interface, without jumping to another tool or re-entering project information.
Acceptance Criteria:
The estimation overview screen launches as a continuation of the same scoping workflow (not as a separate tab or redirect).
Estimation cannot begin until required scoping inputs (e.g., offerings selected, delivery plan, duration) are complete.
Scoped work items and project metadata are auto-carried into estimation without any user re-entry.
Project duration inputted during scoping determines project size for estimation
Offerings selection during scoping will inform model selection
Do users need to be informed on the models being used?
The scoping and estimation steps feel like a single, fluid experience within one workspace.
Navigation bar reflects where the user is in the scoping/estimation process.
The scoping UI includes a clearly marked button to begin estimation.
Consider areas where estimation inputs can be brought in to the existing scoping flow (i.e. assigning accelerators or ownership directly on the delivery plan page, instead of creating a step in estimation to do so).
If scoped work items are changed, the system requires the user to confirm or save the updated scope before estimation can begin or be resumed.
Carly Hu
