---
title: "Development Methodology"
slug: "how-to-setup-your-development-methodology"
updated: 2021-12-18T20:14:17Z
published: 2021-12-18T20:14:18Z
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, c****hanging naming conventions**, and **a****dding additional entities**.

**Important!** Any Release Dynamix Development Methodology changes will reflect **all projects** across**all systems**.

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

1. [Login to Panaya](/v1/docs/how-to-log-in-to-panaya)
2. Click on the **Settings button ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639651164147.png)**to open up the Settings panel, then select **Configuration.**
3. Verify that the relevant **System**is selected in the drop-down list  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639651177139.png)
4. In the **Release Dynamix** section, select to **Manage Development Methodology ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639651187085.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-1639651199244.png)

---

## Customization

1. To define the terms appropriate to your existing terminology, click on **Customize.**![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639651209007.png)****
2. **You can change the naming for Level 2 and 3 activities to meet your existing convention.**
3. You can **add other entities** for similar activities, click on the plus button![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639651225723.png)to add entities, set the entity name, and click **Apply**.  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639651239277.png)
4. Upon completion, click **Apply** and then  **Save**

You can add multiple Requirement / Feature types and customize their names (e.g., Innovation Requirement, Enhancement Feature, etc.). 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) according to your needs (currently supported for Level 2 and 3 only).

## Related

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