Application Backlog view

  • Release version: Xanadu
  • Updated August 1, 2024
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Application Backlog view

    The Application Backlog view is designed to help enterprise architects monitor and manage the work impacting business applications within a scrum framework. It provides a centralized timeline combining epics, stories, enhancements, projects, and demands related to applications, enabling streamlined prioritization and sequencing of work items.

    Show full answer Show less

    To access this view within the TPM timeline, the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0) must be activated.

    Key Features

    • Centralized backlog: Displays epics, stories, enhancements, projects, and demands associated with business applications in one consolidated view.
    • Application risk filtering: Lists all applications by default as high risk, with options to filter based on risk intensity.
    • Flexible timeline views: Allows switching between quarterly and monthly timeline perspectives.
    • Expandable application details: Expands each application to reveal its unified backlog and shows counts of related work items.
    • Clickable records: Epics, stories, enhancements, projects, and demands in the application column link directly to their detailed records.
    • Pagination: Controls the number of applications shown in a single view for easier navigation.
    • Integration with PPM Standard plugin: Enables adding projects to applications; otherwise, demands are created by default.
    • Timeline visualization: Work items are plotted with start and end dates, showing continuous lines or single dates as filled circles if only one date is present.

    Work Item Types Displayed

    • Epics: High-level business goals broken into smaller parts, reflected on the timeline between planned start and end dates; only active epics (not complete or canceled) are shown.
    • Stories: Fundamental work units mostly linked to epics, displayed only if not complete or canceled; timeline corresponds to the sprint dates.
    • Others: Stories not attached to epics but directly associated with the business application are grouped under “Others.”
    • Enhancements: User requests reviewed by product owners and converted into stories; only active enhancements are displayed on their scheduled timeline.
    • Projects and Demands: Projects appear if PPM Standard plugin is enabled; otherwise, demands are created by default and shown on the timeline.

    Important Considerations

    • For epics, stories, and enhancements to appear in the timeline, they must reference the associated business application.
    • The risk column reflects risk levels only for business applications, not for individual work items like epics or stories.
    • Clicking on items in the application column opens their detailed records in new tabs for deeper inspection or edits.

    As an enterprise architect this view helps you to understand the epics, stories, and enhancements, which are the units of work in scrum, that impact your business application.

    Note:
    Activate Agile Development 2.0 (com.snc.sdlc.agile.2.0) plugin to get the Application Backlog view in the TPM timeline.

    Application Backlog view helps you to look into the centralized backlog of records that are of different task types such as epics, stories, and enhancements. This view facilitates prioritizing and sequencing of different task type records in one location, saving you from sorting and filtering them in many steps. In this view, you can:

    • View all applications (first column) that are at a high risk by default, however you can filter based on the intensity of their risk in the second column.
    • Filter the application records by any attribute in the business application table. Switch to either quarterly or monthly view of the timeline (third column).
    • Create a project or demand to add to the application.
    • Paginate the number of applications to be displayed in a single view.
    • Expand the business application to view its unified backlog of epics, stories, enhancements, projects, and demands attached to the application. You can also see the total number of these entities within brackets.

    You can view the following application backlog entities on the timeline in addition to the projects and demands attached to the application:

    Figure 1. Application Backlog view of the timeline
    By Application Backlog view of the timeline
    Epics

    The high-level business goal of the application is broken down into one or more epics. Epics organize the work required to complete parts of the application goal in small pieces. Epics are further broken down to stories, which are fundamental units of work, that describe the business requirement briefly and can be completed within a sprint. The timeline for the epics is displayed based on the planned start date and planned end date of the epic. The status of epics must not be in Complete or Canceled state.

    Stories

    Stories usually are part of an epic. The stories contained in the epic attached to the business application that are not in Complete or Canceled state are displayed in the timeline. The timeline starts with the planned start date and ends with the planned end date of the sprint to which the story is tagged.

    Others

    There can be stories that are not attached to an epic but directly associated to the business application itself. Such stories are listed within the epics as Others and displayed in the timeline.

    Enhancements

    Enhancements are special requests that come from users with non-scrum role. A scrum product owner reviews these requests and creates one or more user stories. Enhancements in Closed Complete, On Hold, and Canceled state are not displayed in the timeline. The enhancement timeline runs from the Planned start date to its end date when the sprint work is scheduled to begin and end.

    Projects

    If the PPM Standard (com.snc.financial_planning_pmo) plugin is activated, then you can add a project to the business application.

    Demands

    If the PPM Standard plugin is not activated, then by default, a demand is created.

    Note:
    For the timeline to display the epics, stories, and enhancements, each of these records should reference the business application attached to it. See Associate epic to business application for more information.
    Application column

    All the epics, stories, enhancements, projects, and demands listed in the application column are clickable. Clicking each of them opens the record in a new tab that the clickable field points to.

    Risk column

    Shows the risks of the business applications only and not the risks of epics, stories, enhancements, projects, or demands.

    Timeline column

    The start and end dates of the units of work attached to the business application are plotted as a continuous line. However, if only one date is present, either the start or end date, then just that date is plotted as a filled circle.