Portfolio Item Dependencies
SAFe Program & Solution Board Updates
Manual Activities Flexibility
Project Creation Wizard
|Portfolio Item Dependencies||✓||✓|
|SAFe Program Board Updates||✓|
|SAFe Solution Board Updates||✓|
|Data Mart Updates||✓||✓|
|Other Continuum Enhancements||✓|
|New ALM Connect Integrations||✓|
|System Requirements Changes||✓||✓||✓||✓|
How to Upgrade
|If your system is not in the auto-upgrade program, contact support to be added to the program or to schedule your upgrade.||Oct 28||Oct 28||Nov 4||Nov 4||N/A||N/A|
|Contact support for a new 2017 annual license for your on-site system.||Download||Download||Contact Us||Contact Us|
If you are not a current customer, email us at firstname.lastname@example.org to get started.
Tagging is a lightweight, flexible way for different groups to organize data according to their needs. As a user types, suggestions will be presented to attempt common tag usage. For those situations where multiple tags have been used such as "automation", "automate" and "autonation" a project admin or higher can merge those tags into one tag. This will allow for easy administration of tags rather than having to use the API or manually touch each asset. Once tags have been assigned, a user can view them in the grid and also on the asset. A grid view can also be filtered by a tag or multiple tags to narrow down the grid view quickly. To see all assets using that tag, simply click on the tag which triggers an advanced search.
- Portfolio Items
- Test Sets
- Regression Tests
Portfolio Item Dependencies
When planning a future PI or Product Release, the Product Team is often aware of Feature dependencies. Using the new Portfolio Item Dependency relationship, you can identify, capture, and manage dependencies as soon as they are identified without needing to create stories. These dependencies can be set at any level in the Portfolio Item hierarchy. Therefore, you can also create dependencies between Capabilities, Epics, Initiatives, or any level in the hierarchy. Once created, these dependencies can be viewed on the Portfolio Item Dependency Diagram and on the Portfolio Item Relationship Visualization Tab. There is also a new Open Portfolio Item Dependency report for those who like to see these dependencies in a tabular form.
SAFe Program Board Updates
When planning a Release, or a Program Increment, the Program Board provides insight into cross-team dependencies that impact feature completion. Using this information, organizations can reduce the synchronization and coordination issues that occur when developing in a multi-team environment. In order to get the necessary insights, Teams need to operate on a common cadence; and this is not always possible. To solve this problem, the SAFe Program Board in Lifecycle has been enhanced to include date options that allow the end user to define the cadence being used when rolling up work from multiple teams. This cadence is independent of the cadence, or Sprint/Iteration schedule, being used by the Teams to complete work. If your Teams already operate on a common cadence, or Sprint/Iteration Schedule, the date options can be used to specify a cadence that is different if necessary. When Lifecycle detects multiple schedules in the selected context, as defined by the global planning level selector, it automatically enables the date options. When using the date options, columns on the Program Board represent the defined cadence and rows remain the same (Teams). Card placement is based on the end date of the sprint/iteration where the Backlog Items are assigned.
SAFe Solution Board Updates
The Program feature in Lifecycle is a powerful way to group related nodes in a planning hierarchy independent of the defined hierarchy. This feature is commonly used to report on a Solution comprised of Releases, SAFe Programs, or Teams, that are not arranged hierarchically. The Solution board has been enhanced to improve visibility on Portfolio Item completion and significant upstream dependencies identified in a Lifecycle Program. This knowledge enables you to focus on the cross-organization communication and synchronization that matter most for successful Solution delivery.
The "Solution Board" was previously referred to as the "Value Stream Board". The name was changed in SAFe 4.5. Existing Lifecycle instances will continue to use the old term. If you want to use the current term, "Solution Board", you can make this change on the Terminology Page.
Providing guidance to features and alerts to new releases has been in place for hosted instances since earlier this year. This capability is now available for on-site customers as well. From time to time, individual users may see alerts letting them know about features that may be helpful to them as well as more general notices about new releases or other announcements. This guidance is based on the usage of each member, so it requires anonymous usage tracking to make it all work. On-site customers have the option to disable feature guidance and the anonymous usage tracking in cases where the system is used in a secure environment that does not have internet access. Disabling can be done either during install/upgrade or through the application menu by a system Administrator using the Administration > System Administration > Configuration page in the Enable Features section.
The inline reports have been relocated, when a report is available on a particular page the reports button will reflect that reports available. For example on the backlog page it will read "1 on this page." This results in more vertical space available on the page while still presenting inline reports.
You can now configure whether the submenu (second level menu) is visible or not. If you prefer to use this way to navigate the app, you can leave it visible, or you can hide it to reclaim vertical space on the page. The setting can be found under user LifeCycle Preferences ("Show Submenu").
The following changes were made to support Portfolio Item Dependencies.
- Added Data Source Portfolio Item Dependencies
The following changes were made to support Portfolio Item Dependencies
- Added table Bridge.EpicDependencies
Continuum: Delivery Forecasts
The progression board now provides a "Delivery Forecast" for each package revision in a given phase. The forecast is provided in days and it calculated based on the past delivery performance for this particular package as well as the current phase where the package revision is located. The more deliveries the package undergoes, the more accurate the forecast will be. This powerful feature enables release/product/development managers to better forecast value delivery to end users based on real data.
Continuum: Environments Dashboard
The "Environments" perspective in Continuum has been expanded to include a visual dashboard which shows all the existing environments that are active in your Continuum instance. Keeping track of "what's deployed where" is challenging as you scale the number of concurrent projects and deployments; the environments dashboard will make it easy for developers, testers, and product managers alike to quickly find the environments that contains the code they're looking for.
Continuum: Manual Activities
When implementing your value stream via a Continuum progression, users are able to create independent manual activities in-line without having to leave the progression configuration screen. Before this release a pipeline had to be created to stand in for every manual interaction in a progression. This means users will no longer have to leave the progression configuration section to create manual steps. Finally, enhanced activities will allow users to indicate when they have initiated a manual activity but have not completed it yet, eliminating potential double-effort by another user.
Continuum: TeamForge SCM Integration
Continuum now supports TeamForge SCM for both Git and Subversion repositories. Teams using TeamForge SCM are now able to take advantage of Continuum to gain complete visibility into the flow of TeamForge artifacts through the various phases of development as well as metrics, automation, and more (TeamForge SCM ver 17.11+ required)
Standing up a new project used to be a time-consuming endeavor which meant not only creating the project and configuring it in Continuum but also going into your version control system, locating the relevant repo to match to the project, and configuring the relevant webhook URL to communicate with Continuum. The new project creation wizard does all of this for you, right within Continuum. Simply specify the VCS and repo to be used for the project and Continuum will do the rest.
Continuum: Outbound Webhooks
Continuum can now notify external systems when the following events take place:
- Pipeline Instance Status: Provides information whenever a pipeline instance changes status.
- Task Instance Addition: Provides information whenever a task executes.
- Change Submissions: Provides information on all change submissions received by Continuum. The payload includes all the original content coming from your version control system and it additionally provides Continuum-specific data along with the original payload headers.
This is useful for Continuum users who are currently using an external aggregation or alerting tool.
Continuum: Other Enhancements
- TFS integration now supports multiple collections with no default
- TeamForge ALM integration has been updated to support versions 6.0 to present
- Subversion integration now supports file object risk which enables to the use of "Risk" progression metrics
New Systems Added:
Jira Service Desk
System Requirements Changes
No Changes. See Lifecycle System Requirements for details.
This release bring even more additional filters. We have now added asset relationships as filters on different grids. This means that you can now filter by "Created By", "Changed By", "Product Owner" and many more filters.
For a complete listing of point releases, see Point Release Notes by Product.