Skip to main content
System StatusContact Support
VersionOne Community

What impact does defining a team process have on my instance?

Overview 

Learn what areas of Lifecycle are impacted when you define a team's process.

Impact to Sprint/Iteration Tracking Storyboards

The Storyboard presentation and behavior changes when teams have enabled the Team Process Management feature to manage their own process.  These changes are driven by the page-level Team filter.

  • When filtered to a team with a defined process, storyboards configured to show Status values as columns, display the Status values defined by the team.  You can use drag and drop to move backlog items between any visible Status value.

  • When filtered to a team that does not have a defined process, storyboards configured to show Status values as columns, display the Status values defined in the Project Workspace for the selected project.  You can use drag and drop to move backlog items between any visible Status value.

  • When filtered to the "None" teams, storyboards configured to show Status values as columns, display the Status values defined in the Project Workspace for the selected project.  You can use drag and drop to move backlog items between any visible Status value.

  • When filtered to "All" teams in a project where no team has a defined process AND there are no Project Workspaces defined for child projects, storyboards configured to show Status values as columns, display the Status values defined in the Project Workspace for the selected project.  You can use drag and Drop to move backlog items between any visible Status value.

  • When filtered to "All" teams in a project where at least one team has a defined process, or there are Project Workspaces defined for child projects with differing Status values, storyboards configured to show Status values as columns, display Rollup Categories as columns and the drag and drop functionality is disabled.

Impact to TeamRooms

In TeamRooms, backlog item Status values are available in grids, storyboards, and on reports. The behavior documented above is the same in TeamRoom. The only other change in TeamRooms is added support for the "All" Team. When you select this filter, all backlog items are considered regardless of team assignment.

Impact to Grid Status Value Filters

In grids:

  • The values listed in the backlog item Status filter on grids will change depending on the team filter. 

  • When the grid is filtered to a team with a defined process, the Status value list is populated with values from that team.

  • When the grid is filtered to a team without a defined process, the Status value list is populated with values from the Project Workspace for the selected Project.

  • When the grid is filtered to the "None" team, the Status value list is populated with values from the Project Workspace for the selected Project.

  • When the grid is not filtered for a team, the Status value list is populated with values from the Project Workspace and then with the Status values for Teams with a defined process that own backlog items in the project.

Impacts to Reports

The Team Process Management feature has an impact on Status based reports.  However these changes are only slightly different that what Teams experience today when Status values change in Project Workspaces.  The impacted reports are Cumulative Flow and Cycle Time in Lifecycle and Analtyics and the Time In Status reports in Analytics. 

Cumulative Flow by Status

With the introduction of Team Process Management, the Cumulative Flow by Status chart will report based on roll-up categories anytime it detects multiple Status values definitions.  This will occur in two scenarios.  First, when the selected Project/Planning Level contain Backlog Items assigned to one or more Teams with a defined process.  Second, when the selected  Project/Planning Level spans multiple Project Workspaces with different Status values enabled. 

  • When filtered to a Team that has a defined process, the Cumulative Flow by Status chart will always report based on the Status values defined for the Team. 

  • When filtered to a Team that does not have a defined process, the Cumulative Flow by Status chart reports based on the Status values defined for selected Project Workspace.  If the chart detects distinct Status values enabled in multiple Project Workspaces, it will switch to roll-up categories. 

  • When filtered to show Backlog Items not assigned to a Team (the "None" team), the Cumulative Flow by Status chart reports based on the Status values defined for selected Project Workspace.  If the chart detects distinct Status values enabled in multiple Project Workspaces, it will switch to roll-up categories. 

  • When filtered to show all Backlog Items regardless of Team (the "All" team), the Cumulative Flow by Status chart reports based on roll-up categories, unless the chart detects that all Status are enabled in the Project Workspaces. 

Workitem Cycle Time

In order to calculate Workitem Cycle Time, you must specify the Begin and End Status Value that defines the cycle you wish to measure.  As such, the All filter is no longer available.  When filtered to a Team with a defined process, this Status value dropdown is populated with the values defined by the Team.  All other Team filters populate the list with values enabled in the Project Workspace for the selected Project/Planning Level and all child levels.

Time In Status Dashboard Panels

The Time In Status Dashboard panels have a Status filter that is populated with values based on the Team filter.  When filtered to a Team with a defined process, the list is populated with the values defined by the Team.  All other Team filters populate the list with values enabled in the Project Workspace for the selected Project/Planning Level and all child levels.

The Team Process Management feature was introduced in the Spring 2017 Release (17.1). This feature is not available in prior versions.

  • Was this article helpful?