Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.

StarTeam Agile 2.0 is released this month

Micro Focus Expert
Micro Focus Expert
1 0 2,749

This month see’s the release of StarTeam Agile version 2.0. See below for a breakdown on what is new in Agile 2.0. 

Capacity Planning

  • Default Capacity You can now set users default capacity (hours) for a project. By default, every new sprint will assume that capacity for the user.
  • Override Capacity Per Sprint Users can override their capacity on a sprint by sprint basis, making it easier to adjust capacity in case of absence for any reason.
  • Capacity indicator within Tasks Creation If capacity is set, the Task Owner list now includes a indicator listing if the user you are assigning the task has available hours (green) or if the user is already over his capacity (red).
  • Capacity Chart within People Filter (Teamboard)
    • The Team Member card in the Team Filter panel now shows a capacity chart that fills accordingly with the user’s capacity availability. 
    • If you hover over the capacity chart, StarTeam Agile displays an insight tool tip with both capacity (Percentage and hours details) and involvement (Percentage and points details) data to show the user’s workload and how much of the sprint is dependent upon them.
    • If the user is over capacity a red indicator is shown on the Capacity Chart
  • Insight Team Burndown and Individual Burndown Capacity Lines
    • Both Team Burndown and Individual Burndown charts now include an additional line to represent the capacity.
    • The capacity line in the burndown changes color accordingly with the allocation (blue if effort is under capacity, red if the effort is over capacity)
  • Teamboard Task Cards Over Capacity Indicator
    • When tasks are assigned to a user that is over capacity, the task cards show the owner label as red.
    • If you hover a task card with an owner over capacity, the hover will contain an indicator explaining how many hours over capacity the owner is.

 Backlog Breakdown View

The Backlog Breakdown View has been introduced to replace and enhance the Hierarchy View on the backlog. The new breakdown view allows you to not only organize and manage your hierarchies but it also allows you to track progress of children items within a hierarchy.

  • You can now filter based on the entire hierarchy, not only top level items. That way if you have child items that match the filter criteria StarTeam Agile will return those hierarchies for you as well.
  • Sprints are now part of the filtering criteria so you can actually look at the hierarchies that have children allocated to a particular sprint.

 Teamboard List View

The teamboard now offers two views, a card view (available in the previous release) and a new flat list view. The list view can be expanded to view both Stories and Tasks in the Sprint and can also be used to edit the Task Status or change a story to Accepted from within the list.

  • Within the List View, you can now execute CarryOver to Sprint and Move to Backlog operations on single items.
  •  Within the List View, you can also execute bulk operations (multiple stories) like: CarryOver to Sprint, Move to Backlog, and Set Target Release for a Story. Story Acceptance

Stories now have an Accepted state, so users can differ from stories that have their work completed but have not accepted, and stories that have been accepted.

  • When a Story is marked Completed, the Story Card will have an added slider button that says Completed. To change the story to Accepted, simply click the button and the Story Status will be updated to Accepted.
  • You can track Accepted/Completed on the Insight Panel (Teamboard View) and the Story Cards in the Sprint Panel.

Cross-Release Sprints

Sprints are no longer bound to releases, that way you can have stories that are targeted to multiple releases within a sprint. The Sprint Planning panel has added a Show All option in the Release list so that all sprints for a project can be selected. Sprints can optionally be assigned to a release as well and the list will allow the user to filter the Sprint Planning panel by each release if needed.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.