Product backlog

Data in Agile Manager is first divided into Workspaces. Site administrators can create multiple workspaces to represent multiple projects, programs, or products managed on the same Agile Manager site.

Administrators can also assign users to one or more workspaces and define workspace administrators to configure specific settings. Users can only access workspaces that they are assigned to. Data cannot be shared or viewed across workspaces, and users switch back and forth to view data in different workspaces.

Releases and teams are also structured within individual workspaces, and do not cross workspaces.

The following diagram illustrates how items are organized in a workspace.

Themes are the top-level objectives your product must meet, or the product's high-level functional areas. Themes are implemented across releases.

  • Themes are broken down into Features, which are the areas of a product typically implemented within the scope of a release.
  • Features are further broken down into Backlog Items, which are the user stories developed and defects fixed by your teams.
  • Features and backlog items are developed during the scope of a Release, by members of a specific Team.
  • Themes, features, backlog items, and teams can all be associated with specific Applications. Applications are the different components developed by your teams, and can be used to hide data that isn’t relevant to you from in grids, graphs, and widgets.

Application inheritance

The following diagram illustrates how an association with an application is inherited from a theme or feature’s child items.

 

 

When a backlog item is associated with an application, its parent feature and theme is also associated with that application.

Features can consist of several backlog item, implemented in several applications. By the same token, themes can consist of several features, each associated with one or more applications.

Individual backlog items can be associated with only a single application.

See also: