We've been evolving in the application transformation world and adapting to Agile and DevOps principles, as I'm sure your organization is, too. Our goal now is to make it enterprise ready across our different business units, adapting Enterprise Agile framework.
On top of being part of these exciting application transformations, I'm part of the ALM Octane RnD team, integrating customer feedback and market trends into our product that manages agile development and end-to-end delivery – ALM Octane.
In the early days of ALM Octane development, before it was even in beta mode, we - the RnD team - were the only team managing our development process using ALM Octane. During the early days, as is the case with any new product, there were some product gaps, but we forged ahead with tight collaboration between the different roles: product managers, product owners, developers, testers, program manager and others.
At that time, we didn’t have robust administration rules in the system and every user could change anything in the workspace. We trusted each other not to delete defects, not to add features to the backlog, and for sure not to change priorities. It didn’t last long! Controlling such a large group became impossible, and you can imagine the discussions when a defect priority was changed – or even deleted – with no viewable history to understand who did it. What a nightmare!
That time has passed. ALM Octane is now two years old, being continuously delivered with monthly updates and quarterly releases. And last week, we launched a brand new version: ALM Octane CP7.
This release addresses the key functionality: Custom Roles & Module Access. You can now configure user permissions per role, defining who can add new epics and features, who can prioritize them, who can close defects or postpone them to the next release, who can decide which backlog items to flag as work in progress, and more.
Each user is assigned to a role. ALM Octane includes several out of the box roles, but new roles can be freely added. In the image below, you can see the “Team Member” role and its permissions in the testing area. For example, a team member can create a new manual test or add new comments. They can delete only tests that they created. All the settings can be changed, and a new custom role can be created based on the tester role settings.
Similarly, ALM Octane modules can be hidden for the Team Member role, to allow for a more focused interface. In the image below, access to the ‘Backlog’ module was removed, as was access to 'Pipelines', which is more relevant for developers.
Deleting a workspace and all its entities and links is now supported. This is useful when a team has finished evaluating the product and has opened a production workspace. With this new feature, they can now clear all the playgrounds.
Automatic emails sent by ALM Octane can now be customized with your own header and footer. In general, email notifications are fully customizable and are sent based on the business rules that you define.
LDAP users can easily be added to ALM Octane workspaces. Users can be found using wildcards in the name search.
Customers who used ALM Octane with the internal user management can switch to an LDAP-based solution. The existing and LDAP users will be auto-merged.
We look forward to hearing your feedback on our enhanced Enterprise Readiness features.
Talk to us in the ALM Octane community
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.