Concourse Feedback

Put Simply:
For long-running tech implementations like SAP, Workday, or Oracle, teams often structure work in distinct phases or releases. Scoping needs to support this reality by allowing users to break work into scoped phases—each with its own timeline, set of deliverables, and recurring work items (like QA or UAT).

Why It Matters:

• Reflects how work is delivered: Large-scale projects are rarely delivered all at once. Teams plan, build, and release in waves—scoping should reflect that.

• Improves planning accuracy: Helps teams focus on scoping what’s actually going to be executed in the near term, without losing visibility into later phases.

• Enables recurring work: Supports delivery patterns where cycles like QA, UAT, or cutover need to occur multiple times across releases.

• Supports agile and hybrid delivery: Accommodates a more iterative approach, which is increasingly common even in traditional tech enablement programs.

• Enhances client communication: Makes it easier to set expectations by clearly showing what’s happening in each phase of delivery.

What’s Needed:

• UI for defining phases/releases during scoping (e.g., Phase 1, Phase 2, etc.).

• Ability to assign deliverables and tasks to specific phases.

• Support for recurring activities tied to each release (e.g., multiple rounds of QA/UAT).

• Timeline and estimation for each phase to inform planning and downstream tools.

• Backend updates to scope service and delivery models to store phase-level data.

• Potential visual cues or filters in delivery plan and scope views to show or switch between phases.

• Admin configuration options to define standard phase templates for common engagement types.