Table of contents
- Release Summary Video
- Planning Rooms
- Other Epic-Related Changes
- SAFe (TM) Reporting
- New Community Site
- Platform Updates
- API Changes
- System Requirements Changes
|Other Epic Changes|
|SAFe (TM) Reporting|
|Other Analytics Changes|
|New Community Site|
|System Requirements Changes|
Contact your account manager* to upgrade your On-Demand system.
*Lost your account manager’s contact info? Email us at Info@VersionOne.com.
Data Model Changes
This release contains a number of data changes that will impact your usage of Conversation and Expressions. Please read the below release notes carefully prior to upgrading for details on the changes.
Release Summary Video
Sit back and watch as we walk through the major features of this release. The Release Summary video includes segments on:
- Planning Rooms
- SAFe(TM) Reporting
A Planning Room provides a focused location for planning, collaboration and progress visibility to program and portfolio planning teams who need to create and manage functional plans. Groups who plan at different levels of your organization can each create their own Planning Rooms and configure them to focus on their respective areas of responsibility.This allows your organization to define separate Planning Rooms for, say, your Steering Committee, Product A planning group, Product B planning group, Security Component planning, and so on. The organization can create as many rooms as needed.
- An Epic Tree, which provides full customizatation, filtering and decomposition capabilities
- Two Epicboards, which allow for focus to be configured for different levels of your organization
- An Epic Timeline, which includes all filtering and publishing capabilities
- Planning Room Conversations, which include room-specific conversations as well as conversations on epics within the room's project scope
Planning Rooms are similar in model to the Teamrooms and fit into the same access methods. The My Teamrooms link in the utility bar has been changed to My Rooms, with separate sections for Planning Rooms and Teamrooms of which the user is a member. Similarly, the Teamroom Lobby in the My Home area has changed to be the Room Lobby, with separate lists of all accessible Planning Rooms and Teamrooms.
Other Epic-Related Changes
Additional updates have been made to strengthen the structure within the epic tree and improve the flexibility in the epic views to provide better support for enterprise-level planning.
Stronger Epic Type
The Epic Type designation has been elevated in stature to better allow for distinction between the levels of your feature hierarchy. Configure the Type to match the terminology and number of levels you use in breaking down features. For example, epic tree levels in an organization may include: Initiatives, Features and Sub-Features. Changes made to support this include:
- Type field has moved up to the top grouping on detail views and add/edit pages.
- Type field is available as a filter in all epic planning views: Epic Tree, Epicboards, Epic Timeline.
- Type field can be used as a configuration setting for Planning Room Epicboards to default the view to a designated functional level.
Better Epic Filtering
Filters have been enhanced across the Epic Tree, Epicboard and Epic Timeline to provide a larger and more consistent set of filtering options. These filters are available in both the vase views under Product Planning as well as in the Planning Room views.
Conversations+ enriches collaboration by expanding the pool of people who can actively participate within Conversations. You can now collaborate with people even if they're not currently VersionOne members by inviting them through email. There are two different ways to invite a guest collaborator:
- by mentioning them from any conversation. Suppose you need input from someone in another part of your organization who isn't already using VersionOne. Enter their email address in the mention component to invite them and include them within that conversation as if they were a regular member.
- by including them into a Conversation Space. Similarly to how you would invite a member to a conversation, you can invite a guest collaborator to a space.
Once a guest collaborator registers with the system, they will only have access to the conversations they've been invited to. They will not have access to any secured assets nor will they have access to any of the user interface other than a specialized Conversations page. Guest Collaborators will not consume a license though they can be promoted to a fully licensed member by your member or system administrators.
SAFe (TM) Reporting
Several new Dashboard panels and charts were added to improve the tracking of your Enterprise agile initiatives. These reports are part of the Scaled Agile Framework but are valuable regardless of methododolgy.
For Team level tracking, we've added the following panels
- Velocity Trend showing planned and actual. Unlike our existing velocity trend panel, this panel has a bar to indicate the number of story points that were planned on the iteration begin date and the number of story points closed at the end of the iteration.
- Story Count by Iteration. This panel shows the number of stories that were planned at the beginnning of the iteration and the number of stories closed at the end. This panel also indicates what percentages of planned stories were closed based on counts.
- Defect Trend by Iteration. This panel is similar to our existing Defect Trend chart; however in this chart each bar represents an iteration. This allows you to see how your Defects changed after each iteration.
- Test Trend by Iteration. This panel is similar to our existing Test Trend panel. However, in this panel, each bar represents an iteration. This allows you to see how your Tests changed after each iteration.
For Program level tracking, we've added
- Feature Velocity Trend. This panel shows the number of features planned at the beginning of a release and the number of features closed at the end. Since planning does not happen on the first day, this report supports a Planning Offset parameter. This paramer allows you to specify how many days past the Project Begin date should be skipped before considering the project planned.
- Feature Completeness. This panel indicates how features are tracking towards plan. For each feature in a project, the report indicates the percent complete expected for the specified date and the percent complete actual for the same date. Bar colors allow you quickly identify those features that are on track for delivery.
- Story Count by Project. This panel shows the number of stories that were planned at the beginnning of a project and the number of stories closed at the end. This panel also indicates what percentages of planned stories were closed based on counts. Since planning does not happen on the first day, this report supports a Planning Offset parameter. This paramer allows you to specify how many days past the Project Begin date should be skipped before considering the project planned.
For Portfolio level tracking, we've added
- Epic Test Trend. Success criteria for Epics can be defined as Tests on Epics. This panel allows you to track the status of those test over time.
Finally, we've added a dashboard panel that can be used to display a Custom Report. Using this panel, you can now display a Custom Report along side the built-in panels.
Other Analytic Changes
In addition to the Enterprise Agle changes specified above, Analytics received the following enhancements:
- Two new data objects were added to Custom Reports
- Epic Test Details. This data object contains the current attribute values for Test on an Epic.
- Epic Test Trends. This data object trends changes on Test defined on an Epic over time. You can trend Type Changes, Status Changes, State Changes, and changes to custom fields.
- A new sample report was added that shows planned and actual Velocity. This report demonstrates how to use the SQL Case statement to create a calculated column.
Data Mart Database Changes
The following tables were added to the Data Mart database:
- Dim.EpicTest. This table contains the current attribute values for Test on an Epic.
- Fact.EpicTest. This table trends changes on Test defined on an Epic. You can trend Type Changes, Status Changes, State Changes, and changes to custom fields.
New Community Site
Online self-help support available on community.versionone.com has been relaunched on a new platform with a greatly improved experience. The new site features consolidated and updated content, better organization, and an improved search. These articles and videos are available through the Support Center > Support link within the application.
The old community site and it's content will be available for a limited time at legacy.community.versionone.com/default.aspx.
Standard documentation is still found inside the application and is under the Support Center > Help menu item; however, we will eventually be migrating to our new community platform.
The RSS feed for new release notifications has changed. Subscribe to the new VersionOne Releases RSS feed to keep up to date on new release availability.
New! UX360 Integration for VersionOne
- Connect user experience research to agile planning and project management.
New! Testuff Integration for VersionOne
- Send defects reported during testing to VersionOne for on-going tracking and planning.
VersionOne Integration for Git
- Added: Listen on all branches and ignore a subset
- Added: Configure names for created changeset assets
- Added: Sample configuration file pointing to working Git and VersionOne instances.
- Update: JGit and VersionOne libraries
- Update: now using Java Service Wrapper
- Improved: Logging
SDK.Java and SDK.NET API Client
- Fixed: Save Method allows new assets to be saved when OID is null and no attributes have changed
SDK.Java and SDK.NET Object Model
- Changed: Conversation and Expression assets reflect changes in core API.
VersionOne Integration for CruiseControl.NET
- Update: VersionOne libraries
VersionOne Provisioning for LDAP
- Update: VersionOne libraries
- QuickTest Pro - sunsetting as of Spring 2014.
- SmartBear Test Complete - sunsetting as of Spring 2014.
This release contains breaking changes to the API.
Core API Updates
New: Conversations as first-class citizens. Prior to this release, threaded conversations were constructed from Expression queries and an implicit understanding of their relationship to one another. With this release we introduce a formal Conversations asset to better align the API and UI to a consistent domain model.
- ExpressionSpace : Relation to ExpressionSpace — reciprocal of AssociatedConversations
- Participants : Multi-Relation to Member — reciprocal of ParticipatesInConversations
- Room : Relation to Room — reciprocal of AssociatedConversations
- ContainedExpressions : Multi-Relation to Expression — reciprocal of BelongsTo
- IsJoinable : Boolean — validator for Join
- IsLeavable : Boolean — validator for Leave
- MostRecentReply : Relation to Expression
- Topic : Relation to Expression
- Viewers : Multi-Relation to Member
- Join : operation — validated by IsJoinable
- Leave : operation — validated by IsLeavable
- AssociatedConversations : Multi-Relation to Conversation — reciprocal of ExpressionSpace
- Expressions Multi-Relation to Expression — reciprocal of ExpressionSpace
- ParticipatesInConversations: Multi-Relation to Conversation — reciprocal of Participants (Previously was a relationship to Expression)
- AssociatedConversations : Multi-Relation to Conversation — reciprocal of Room
- Expressions : Multi-Relation to Expression — reciprocal of TeamRoom
- BelongsTo : Relation to Conversation — reciprocal of ContainedExpressions
- ExpressionSpace : Multi-Relation to ExpressionSpace — reciprocal of Expressions
- TeamRoom : Multi-Relation to TeamRoom — reciprocal of Expressions
- Conversation : Relation to Expression
- ExpressionsInConversation : Multi-Relation to Expression
- JoinConversation : operation
- LeaveConversation : operation
.NET SDK Updates
- Changed: Object Model Conversations from old style (Expression) to new style (Conversation)
Java SDK Updates
- Changed: Object Model Conversations from old style (Expression) to new style (Conversation)
System Requirements Changes
The following additions were rolled out in point releases since the last quarterly release:
- Expanded Epic Filter: The Epic filter on the backlog page has now been expanded so that the filtering capabilites equals the flexibility of the Epic Tree view.
- Epic Timeline Administration: Administrators are able to view, filter and manage previously published epic timelines.
- Hosted Support Contact List: Upon upgrading from am older release, members who are System Admins will automatilcally have their member detail email addresses added to a support contact list. This list may be viewed and edited in the Adminstration Configuration page of your hosted VersionOne instance.
- Conversations Usabilty: The Conversations icon in the Asset Hovers have been improved so that they will visually indicate when an asset has conversation activity. Additionally, the ability to start a new conversation directly from the asset hover has been re-implemented. It is now also possible to rename any previously created Conversation Space.
- Conversations Email Notifications: Various improvements to make it easier to understand when to expect emails based on conversations activity. You will receive conversations emails if you are directly mentioned in the conversation, if you are the owner of an asset that is mentioned in a conversation, if you are a participant of a conversation or if you are watching an asset that is mentioned in a conversation.
- Datamart: PrimaryWorkitemProjectKey column to Dim.PrimaryWorkitem table. This column has a foreign key relationship to Dim.Project.
- Datamart: SecondaryWorkitemProjectKey column to Dim.SecondaryWorkitem table. This column has a foreign key relationship to Dim.Project.
- The Effort Quicklist report now includes deleted workitems in the listing when effort has previously been entered for them.
Scaled Agile Framework® and SAFe are registered trademarks of Leffingwell, LLC.