Scope Activation Off-Ramp for Engagements Using Client Delivery Tools

Put Simply
Allow users to finalize and activate their scope without creating a Jira project if the engagement is to be delivered in a client-hosted system.

Problem Statement

Today, Concourse activation is tightly coupled to Jira Cloud provisioning. This works for engagements using PwC-hosted Jira, but creates a major gap when:

• The client requires delivery in their own system (client-hosted Jira, ADO, MS Project, etc.)

• Data security or contractual constraints prevent use of PwC-hosted tools

This results in:

• Unnecessary Jira project provisioning and license usage

• Users avoiding activation entirely to avoid Jira setup

• Inaccurate tracking of “won” work in Concourse

• Export being treated as a secondary workflow instead of a primary delivery path

We need to introduce a controlled off-ramp during activation that:

• Allows users to choose a client delivery system

• Prevents Jira provisioning

• Still finalizes the scope and transitions the workspace to delivery

• Provides export as the handoff mechanism