Idea ID: 2764664

Shared backlog Items

8 Votes
Status : Under Consideration
over 1 year ago

For two big Projects, which are represented in two big (SAFe) workspaces, we have a "shared_services" department that is developing its own monolithic application. This department would like to have its own workspace "shared_Services" in ALM Octane, as it also has to keep its own backlog in addition to the requirements from the two major Projects.

The challenge now is that the backlog items, which originate from  the both Projects, should be visible both in the respective Workspace and in the "shared_Services" Workspace.

Idea:

Please introduce the "Shared backlog items" analogous to the shared Application module.
In workspaces that are members of shared space you can create this new "shared backlog Item".
Shared backlog items are inherited by all workspaces in the shared space.
Users can create shared backlog items.
Users can relate the shared backlog item to a local Feature.
Only the user, who owns the shared backlog, can modify the item.
By means of a Symbol in the board it should be immediately recognizable that it is a shared backlog item.

 

  • We are considering supporting more shared entities (e.g. Backlog).

    However,  for supporting Large Solutions of SAFe (namely a collection of systems\programs) we recommend checking the option utilizing the Program level of a workspace.

     

  • Dear All,

     

    I have Some questions when comparing with ALM 12.55 and ALM Octane

     

    Two questions from "Test Management" Module Perspective:

    ================================================

    1.How "Test Resource Management" is handled in Octane?

    2.How "Test Configurations" is handled in Octane?

    Six questions from "Requirement Management" Module Perspective

    =======================================================

    1. How "Multiple Requirement Types" are handled in Octane?

    2. How "Business Process Models" is handled in Octane?

    3. How "Baselining" is handled in Octane?

    4. How "Risk-based Quality Management" is handled in Octane?

    5. How "Requirements Sharing/Reuse" is handled in Octane?

    6. How "Requirements Templates" are handled in Octane?

    Two questions from "Lifecycle Management " Perspective

    =============================================

    1. How "Project Planning & Tracking" are handled in Octane?

    2. How "Business Views" is handled in Octane?

    Please clarify.

    Tons of Thanks in advance.