Allow Delivery Map Build Teams to Create their Stages (aka remove BXT names)

Nearly every single time we try to create a new standardized delivery map for one of our Integrated Solutions or Practice Teams, our client team members building the delivery map ask to remove the BXT agile stage names. They explain that we don't execute our work using the BXT agile process. Instead they want to name the stages by phases of the project, category (e.g., Admin, Project Management, Deliverables, etc.), or sub project within the larger SoW or EL.

However, the delivery map build team continues to tell us we need to use the BXT agile stages, even if that's not how are teams execute their work.

This in turn leads to the delivery maps being published with those stages and then the end users are frustrated and they end up renaming the stages when they create their Concourse workspace. This isn't the best use of their time and it's creating inconsistencies among how our teams are using our published/golden copy delivery maps.

Plus, many of our teams after they rename the stages use that metadata field for status reporting. BXT Agile stages: Align, Innovate, Release, Evolve are not descriptive enough to provide us the insight we need for reporting.