Releases are formally planned by matching change requests and new projects against capacity, timing, and priority.

Upon approval, changesets and tasks are generated for teams to execute.

This approach fits very well in a traditional development model or applications where stability and reliability requirements and complexity are high

release management


Use of cookies

This web site uses cookies to give you the best user experience. If you continue browsing you are giving your consent for the acceptance of the aforementioned cookies and the acceptance of our cookies policy, click at the link for more information. ACEPTAR

Aviso de cookies