It is easy to configure Panaya to work seamlessly with your existing application life-cycle methodology and terminology.
This article will cover the Development Methodologies, changing naming conventions, and adding additional entities.
Important!
Any changes to the Release Dynamix Development Methodology will be reflected across all projects and systems.
Click the Settings button to open the Settings panel, then select Configuration.
Verify that the relevant System is selected in the drop-down list.

In the Release Dynamix section, select to Manage Development Methodology

Development Methodologies
You can select from two principal Development Methodologies-
Waterfall
Under the traditional Waterfall methodology, Requirements consist of Features, which are split into individual Tasks.
Level 1 - Requirement, Level 2 - Features, Level 3 - Tasks
SAFe / Agile
Under the Scaled Agile Framework methodology, high-level Features are divided into team-level User Stories, then split into individual Tasks.
Level 1 - Feature, Level 2 - User Stories, Level 3 - Tasks

Customization
To define the terms appropriate to your existing terminology, click on the Edit button.

You can change the naming convention for Level 2 and Level 3 activities to match your existing convention.
Adding Activity Type
You can add an activity type for similar activities by clicking the Add type button, setting the entity name, and clicking Apply.

Upon completion, click Apply and then Save
You can add multiple Requirement /Feature types and customize their names (e.g., Innovation Requirement, Enhancement Feature). This will enable an easy differentiation between different types of Requirements.
Such entities can then include custom tabs and fields to suit your needs (currently supported for Levels 2 and 3 only).