---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Development process

# Team Development process {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

The basic Team Development process sets up the instance hierarchy, grants developer access rights, manages the movement of development changes from development instances to test instances, and promotes applications to the production
instance.

## Antes de Iniciar

Role required: admin

## Procedimento

1. Set up the development instance hierarchy as described in [Set up an instance hierarchy](https://servicenow-prod.fluidtopics.net/Uwy8fz5YEbEXzHbWX~1LAA "Set up an instance hierarchy that best supports your development life cycle.").  
   1. Provision development instances on the same software version as the target instance. For example, use the software version that is running on your production instance.
   2. \[Recommended\] Clone the target to the development instances.
   3. For each instance, define the parent instance.
   4. \[Optional\] For each instance, define the peer instances.
   5. For each instance, pull all changes from the parent instance.
   {#t_TeamDevelopmentProcess__ol_snt_dkv_1q}
2. For sub-development instances, grant access rights to appropriate developers.
3. Develop customizations on sub-development instances.  
   Use the team dashboard to track development activities.
   * Pull versions from the parent instance, such as versions that were pushed from other sub-development instances. Reconcile any conflicts with the current local version, as necessary.
   * Track local changes. Queue changes that are ready to push to the parent development instance.
   * Compare versions on peer instances. Reconcile any conflicts.
   {#t_TeamDevelopmentProcess__ul_gwk_nkv_1q}
4. When a feature is ready to promote to the parent development instance, push the current version of the customized records.
5. **Opcional:** Have code reviewers approve or reject the pushed version.
6. Test and promote the feature into production according to your testing and release management process.
**Tarefas relacionadas**   

* [Push a version](https://servicenow-prod.fluidtopics.net/HyiCXpi6q3iQ6Z6oVrfnCQ "Pushing promotes changes from the development instance to the parent instance and commits the current version of a customized record on the development instance as the current version on the parent instance.")  
**Referência relacionada**   

* [Team Development](https://servicenow-prod.fluidtopics.net/t8_qwZjejsDezUKO_UCS_Q "Team Development supports parallel development on multiple, non-production ServiceNow instances.")
* [Access rights for developers](https://servicenow-prod.fluidtopics.net/LeASYylQGbyPR~A4g75iJA "To use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.")