HPE ALM QC - Enterprise Template - In 2015, we created the first version of a corporate enterprise project based on the ALM template functionality. The goal was to standardize fields, lists, workflow, and permissions across the application for all testers. The fourth iteration is currently in production, with a concerted effort to transition approximately 700 ALM repositories to the new template. In addition to creating net-new projects, we are also converting complex projects using the Assure Harmonizer suite of tools.
Why the template functionality? The ALM template allows administrators to make changes on the parent project and replicate those changes to all child projects. In the past, if a new field needed to be added to all projects, a QTP script would be created to add the field, add the list values, and modify permissions. To update workflow, either a .NET script or a support person would need to log in to each project to make the change. With the template functionality, we can make the change in non-production, have it validated, then move the change to production, and replicate to all child projects. This may not sound like a huge savings for smaller instances. However, the enterprise instance has over 700 active projects, 15,000+ named users and daily concurrency of 1,000+. This does not include the second instance, which is about 1/3 the size.
An additional plus is consistency. Having a consistent look, lists, and methodology across the organization allows for standard training, easy trading of resources and better reporting. Reporting is a key portion of the initiative. On non-template projects, the user defined fields may be in different locations on the schema or may not exist at all.
Start it sooner. The biggest help to the project has been the buy-in of senior management, which has been pushing the teams to get involved, make decisions, and take the big picture view point.
