Summary of New Features

TeamRoom

Everything your agile team needs in one place, TeamRoom provides a personalized, simpler yet more powerful interface optimized for teams within your organization. In one page you can see the members of the TeamRoom, useful agile metrics such as planned and average velocity, a velocity chart and iteration burndown. You can also view any combination of toggle-able panels including:

• Project Backlog - a rank-ordered view of what's coming up next.
• Iteration-based views (Taskboard, Storyboard, Testboard or List View) - VersionOne's powerful boards and grid with full functionality.
• Closed items - refer to the team's progress with quick summary of closed items grouped by iteration.
• Conversations - quick access to all of the conversations mentioning backlog items in the TeamRoom.
• Recent Changes - spin up on what's been happening by seeing recently changed backlog items in the TeamRoom.

Other features include:

• Board customizations apply to the TeamRoom. This allows different teams working on the same project to configure their boards differently, for example, to use different WIP limits on their storyboards.
• Clicking a member avatar to filter the boards to show only backlog items that they own.
• A direct URL to a specific TeamRoom which handles showing their backlog via a configured project context.
• The backlog panel helps provide a rough view of how your unscheduled backlog might fall into iterations by grouping backlog items according to how many would fit based on their estimates and the current average velocity.

Relationship Visualization

Increase your understanding of how workitems relate and what is required to complete epics with the new Visualization tab. The Visualization tab is available in the details window for Epics and Workitems (stories, defects, and test sets). You can access this tab directly using the Visualization icon available in the hover.

The Workitem Visualization tab improves your understanding of the context of a workitem. This context includes not just the immediate Epic and Feature Group (Theme), but the entire Epic and Feature Group hierarchy. In addition, you can see Goals assigned to the workitem; this includes Goals assigned directly and those assigned through any Feature Group in the hierarchy. For Backlog Items (Stories), you can also view and navigate dependency relationships. The ability to view more than just the immediate upstream and downstream dependencies allows you to fully understand the impact of a blocking issue or a backlog item broken by a defect. Dependency navigation also allows you to identify circular dependencies.

The Epic Visualization tab improves your understanding of the work necessary to realize an epic. The epic visualization allows you to see the entire epic hierarchy down to the workitem level. The epic visualization also supports zooming in and out of sub-epics. Clicking on a sub-epic will zoom the diagram to that node in the hierarchy allowing you to focus on details. Clicking on the parent epic, allows you to zoom out and focus on the big picture.

Card Aging

Identify cards that are getting stuck so you can increase the flow through your storyboard. Kanban and Agile practitioners can appreciate the new aging feature that allows you to see how long a card has been in a column and in the cycle (cycle must be configured in storyboard to see time in cycle). In addition, you can work to optimize your flow by defining thresholds for both columns and the entire cycle. The storyboard will highlight cards that are either approaching (yellow) or have surpassed (orange) a threshold. Threshold values are configured on a board-by-board basis, so each team can optimize the settings for their specific environment. Note: Thresholds and cycle aging are not available in Team Edition.

Multi-Status WIP Limits

Speaking of optimizing your flow, new group WIP limits on the storyboard literally let you take process optimization to a whole new level. In addition to being able to set Work In Process limits on individual columns of the storyboard, you can now group together columns and add a higher level WIP limit. Perfect for combining queues and activities (e.g. 'Read for Dev' and 'Development') under a single limit, for limiting the number of items within a larger function (e.g. multiple Testing activities), or even for setting a limit across your entire cycle. You can even define multiple Groups across your flow to cover different segments of your process. Much like for column violations, Group WIP limit violation warnings are triggered when dragging over a 'full' group. If you drop the card in a group, the system will highlight the group and all of it's columns, while allowing clear differentiation between group and column-level violations. As with card aging and column WIP limits, Group WIP limits are configured on a board-by-board basis, so each team can optimize the settings for their specific environment.

Analytics Updates

Project Summary Reporting

Project Summary reporting allows you to trend the following project metrics and create calculated fields based on these values. Each value represents a roll-up of the given metric in a project and all child projects on a given date. Additionally, custom numbers, checkboxes, and dropdowns defined Projects are included in this table. Using custom fields you can create values to measure against (baselining), or filter reports based on the value of a custom checkbox or dropdown.

• Total Estimate
• Open Estimate
• Closed Estimate
• Total Detail Estimate
• Open Detail Estimate
• Closed Detail Estimate
• Total Remaining ToDo
• Total Effort
• Count of all Workitems (Story, Defect, TestSet)
• Count of Open Workitems
• Count of Closed Workitems
• Count of Stories
• Count of Open Stories
• Count of Closed Stories
• Count of Defects
• Count of Open Defects
• Count of Closed Defects
• Count of TestSets
• Count of Open TestSets
• Count of Closed TestSets
• Count of Workitem without an Estimate
• Count of all Epics
• Count of all Open Epic
• Count of all Closed Epic
• Count of all Issues
• Count of Open Issues
• Count of Closed Issues
• Count of Requests
• Count of Open Requests
• Count of Closed Requests

Fixed:

• Setup received enhancements intended to improve the administrative task of installing and managing your Analytics instance. These enhancements include a new welcome screen, context sensitive images at each step, links to online help, and easier access to the log files when errors occur. Additionally, we've exposed the ability to use credentials provided by your database administrator and now allow users to change the installation folder. Finally, since Analytics and Data Mart are tightly coupled, you cannot install Analytics until you've installed the Data Mart.

Datamart Updates

Project Summary Reporting

Project Summary reporting allows you to trend the following project metrics. Each value represents a roll-up of the given metric in a project and all child projects on a given date. Additionally, custom numbers, checkboxes, and dropdowns defined Projects are included in this table. Using custom fields you can create values to measure against (baselining), or filter reports based on the value of a custom checkbox or dropdown.

• Total Estimate
• Open Estimate
• Closed Estimate
• Total Detail Estimate
• Open Detail Estimate
• Closed Detail Estimate
• Total Remaining ToDo
• Total Effort
• Count of all Workitems (Story, Defect, TestSet)
• Count of Open Workitems
• Count of Closed Workitems
• Count of Stories
• Count of Open Stories
• Count of Closed Stories
• Count of Defects
• Count of Open Defects
• Count of Closed Defects
• Count of TestSets
• Count of Open TestSets
• Count of Closed TestSets
• Count of Workitem without an Estimate
• Count of all Epics
• Count of all Open Epic
• Count of all Closed Epic
• Count of all Issues
• Count of Open Issues
• Count of Closed Issues
• Count of Requests
• Count of Open Requests
• Count of Closed Requests

Fixed:

• The Data Mart ETL will now truncate long relationship names.
• Setup received enhancements intended to improve the administrative task of installing and managing your Data Mart instance. These enhancements include a new welcome screen, context sensitive images at each step, links to online help, and easier access to the log files when errors occur. Additionally, we've exposed the ability to use credentials provided by your database administrator and now allow users to change the installation folder.

Platform Updates

New SDK.Python (Incubating)

• New: Python wrapper for the REST API. https://github.com/versionone/VersionOne.SDK.Python

SDK.NET

• New: API Client source code available from GitHub. https://github.com/versionone/VersionOne.SDK.NET.APIClient
• New: Object Model source code available from GitHub. https://github.com/versionone/VersionOne.SDK.NET.ObjectModel
• New: SDK DLLs now available from NuGet.
• Fixed: Epics in the Object Model can have Defects and TestSets as children.
• Changed: Sample projects (V1 Tortoise SVN, V1 Task Manager, V1 Estimation Tool, V1 Search) have graduated to independent projects. Source code and binaries are available separately.

SDK.Java

• Fixed: Epics in the Object Model can have Defects and TestSets as children.

Bugzilla Integration

• Fixed: Support for Bugzilla 4.X where Bugzilla::Bug::CountOpenDependencies has been removed.

Clarity PPM Integration

• Added: Maps and processes for Timesheet integration.

JIRA Integration

• Added: Support for JIRA 5.1.

Subversion Integration

• Update: Now using the SharpSVN 1.7 library.

Perforce Integration

• Added: Support for Perforce 2012.1.

Visual Studio Integration

• Added: Support for VS 2012.
• Fixed: Styling of Description pop-up now matches VersionOne UI.

Team Foundation Server Integration

• Added: Support for TFS 2012.

API Changes

None.

System Requirements Changes

Latest browser updates:

• Chrome 22
• Firefox 16

SQL Server:

• Added support for SQL 2012
• Dropped support for SQL 2005

Windows Server:

• Dropped support for Server 2003

Miscellaneous

• Setup received enhancements intended to improve the administrative task of installing and managing your VersionOne instance. These enhancements include a new welcome screen, context sensitive images at each step, links to online help, and easier access to the log files when errors occur. Additionally, we've exposed the ability to use credentials provided by your database administrator.
• A bug was fixed in defining the cycle on the storyboard. For new boards, the cycle appeared to be predefined, but was not truly set until a board configuration change was saved by a user. The UI has been corrected to refrain from indicating a cycle has been set when it has yet to be defined.
• The cycle time report was updated to use the newer, more accurate calculation that accompanied card aging. The new calculation ignores time spent outside of the cycle in between the start and end points and also ignores any intermediate time the card may have been closed.

In addition, the following additions were rolled out in point releases since the last quarterly release:

• Various performance updates.
• Added support for explicit logout when using SSO.
• Catalyst landing page to collect initial project and sprint setup information.