Concourse & Jira DC Portal


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.

Change control process not facilitated

To protect scope during projects and manage the triple constraints (scope - budget - timeline), a form to request scope change is needed to identify the impact and to prevent scope-creep.

  • Guest
  • Sep 5 2024
  • PM Refinement
  • Guest commented
    12 May 08:03pm

    The feature to add additional scope has been released within concourse. Doing this however does not take into account the scope management process, e.g.:

    • Impact on timeline and budget

    • Introduction or mitigation of risks

    • Registration of scope change

    This isn't explicitly related to scope by offerings / building blocks.

  • Admin
    Emma Gattuso commented
    12 May 03:11pm

    Hi Jasper, thanks for your feedback! We are curious to know if this is something you would still be interested in using the scope with offerings flow, now that scope with building blocks is being decommissioned?

  • Admin
    Simon Reid commented
    2 Dec, 2024 03:54pm

    Thank you for your feedback, a Change Control / Scope Change feature is a high priority in our backlog, look to something coming early in 2025!