---
title: "Development Methodology"
slug: "how-to-setup-your-development-methodology"
updated: 2026-08-12T11:11:37Z
published: 2026-08-12T11:11:37Z
canonical: "success.panaya.com/how-to-setup-your-development-methodology"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Development Methodology

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**.

[](/v1/docs/how-to-log-in-to-panaya)

1. Click the **Settings button** to open the Settings panel, then select **Configuration.**
2. Verify that the relevant **System** is selected in the drop-down list.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-BG3525HW.png)
3. In the **Release Dynamix** section, select to **Manage Development Methodology** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-Z8B3LQE1.png)

---

## 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

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-E9QPMZEX.png)

---

## Customization

1. To define the terms appropriate to your existing terminology, click on the **Edit** button**.**![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-6GTRXQUS.png)
2. You can change the naming convention for Level 2 and Level 3 activities to match your existing convention.

---

## Adding Activity Type

1. You can **add an activity type** for similar activities by clicking the **Add type** button, setting the entity name, and clicking **Apply**.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-RN947P3V.png)
2. 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](/v1/docs/all-about-panayas-custom-fields-tabs) to suit your needs (currently supported for Levels 2 and 3 only).

<style> p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data-block-id] { margin-bottom: 0;} blockquote p[data-block-id] {margin-bottom: 0 !important;} &nbsp;p[data-block-id]:empty::after {content: "\00A0";} </style>

## Related

- [Iteration Terminology](/how-to-change-iteration-terminology.md)