The Agile Manager team continues to add and improve functionality to enhance your Agile Manager experience. Now, you can plan and deliver features using Scaled Agile Framework guidelines, use an enhanced ALI configuration wizard, and more.
Plan and deliver features using Scaled Agile Framework® guidelines Agile Manager is now optimized for planning and delivering features using guidelines defined by the Scaled Agile Framework®.
When first defining a feature, set an InitialEstimate in 'shirt sizes'. This helps you easily distribute features per release based on their size. Set this estimate on the feature's Details page.
Prioritize features according to rank (as before), business value, or the full WSJF score.
Estimate a feature in story points. Then, compare the feature's estimated (planned) story points to the release capacity and to the total story points of the feature's backlog items.
Plan features directly to releases by dragging and dropping them into release buckets.
Manage a feature's life cycle through a new feature Status field.
If a feature is too big to complete in a single release, split the feature and assign open backlog items to a future release.
Finally, analyze feature planning and execution using new feature widgets on the Dashboard.
New out-of-the-box defect statuses Use the following new defect statuses as you manage a defect's life cycle: - Set a defect to Deferred if you want to fix it in a later release. - Set a defect to Duplicate if you have another defect for the same issue. A duplicate defect receives the Done backlog item status.
ALI enhancements We updated the ALI configuration wizard's design, usability and functionality. Now you can use the wizard to update existing settings in addition to setting up new configurations.
View details about failed unit tests, including details from the last commit such as the committer and related backlog item. On the Builds page, click a build to view the build report. Click FailedTests to display details about failing unit tests and details from the last commit.
Now you can configure ALI for 2-way SSL for Subversion configurations. Use the wizard or the configuration pages to define your settings.
We improved how ALI handles large data. Data of arbitrary size, such as huge commits and unit test reports, is now reliably synchronized with no errors.
SD00009125 New FeatureOwner field for features. The feature owner can be the person responsible for defining the feature and approving it when complete. SD00023690 Errors fixed for synchronizing defect status changes.
SD00026459 Errors fixed for synchronizing usernames in entity comments.
SD00047097 Performance improvements for feature creation.
SD00034709 Improvements in displaying formatted text that was copied into the Description field from Microsoft Word.
SD00037237 Invalid links to ALM test cases are no longer synchronized to Agile Manager.
SD00040022 Improvements in tenant and username displays.
SD00041566 When breaking a user story with linked items, the links are propagated to all child stories.
SD00045163 Improvements in the FeatureStatus widget display.
SD00048335 Acceptance test statuses are included when exporting acceptance tests to Excel.
SD00048723 Errors fixed for displaying the WatchedItem icon in grids.
SD00049240 Errors fixed for importing backlog items.
SD00053504 Data integrity errors fixed when exporting to Excel.
The recent update in ALM Synchronizer for Agile Manager requires you to download and install the new Synchronizer server and client versions to receive the updates.
1. Uninstall the current Synchronizer server and client. For details, refer to the Uninstall Synchronizer section in the Agile Manager Help Center.
2. Install the new Synchronizer server and client. - In an FTP client, access the following host: ftp://firstname.lastname@example.org/users/agm_rnd/Synchronizer/ForAgM_2.00 - Open the Installation > Server directory and run the setup.exe file. Note: During installation, in the Database Configuration stage, make sure to select KeepExistingDatabase. - Open the Installation > Client folder, and run the HP-ALM-Sync-Client.msi file.
Notes about backup files If you previously used the Link Data Into Backup File option to back up data for specific endpoint links, note that limitations in this release currently prevent you from using this option. Synchronizer regularly backs up the entire database to the <Synchronizer installation>\backup directory. Synchronizer also backs up the database during installation, when you select Keep Existing Database. This backup file is saved to the C:\postgres directory. If errors occur during installation, you can rely on these backup files to restore your database details.