View source for Digital Enablement Development Release Cycle

The Digital Collaboration uses an Agile framework to develop and release digital products.

==Agile==
Agile is an umbrella term for a variety of development methods which focus on adaptability, continuous development, iteration and collaboration.[1] 

==Stages of Development and Release==

DCD uses open-source software to develop applications, and follows four stages for releasing these applications.

===Pilot===
DCD may test multiple open-source applications to develop a particular tool. When a tool is in pilot it means that an open-source application is being tested to see if it can meet the users' needs, before the tool undergoes a more comprehensive development by the DCD team. It is a short-term, experimental phase to see how the large-scale service may work in practice.[https://searchcio.techtarget.com/definition/pilot-program-pilot-study]. Pilot is sometimes referred to as pre-alpha.[https://en.wikipedia.org/wiki/Software_release_life_cycle#Pre-alpha] 

Open pilot testing means that the potential open-source application is available to anyone in the user-base to test. Closed pilot testing means that the potential application is only available internally to the team who will be developing the tool. The DCD team uses both of these pilot testing methods depending on what makes the most sense for the tool which will be developed. However, when possible open pilot testing is preferred as it includes the user at the earliest stage of development and allows the users to provide feedback.

If the open-source application being tested is unsuitable, a different application will be pilot tested.

'''Currently the following tools are in pilot:'''
*Message

===Alpha===
After the appropriate open-source application is selected, the tool undergoes Alpha development and testing. During this phase the features and design of the tool are developed based on the user needs determined in pilot testing. 

Alpha testing is done by select users to test the usability and user experience of the tool in development, as well as to find major bugs which affect the functionality of the tool[https://www.softwaretestinghelp.com/alpha-testing/]. The DCD team also focuses on accessibility testing during this stage.

When in Alpha the tool is functional, but may not include all of the enhancements which will be in the official release. Alpha is complete when all of the necessary features and design are developed and tested, and the tool is ready to be released to the entire user base.[https://techterms.com/definition/alpha_software]

'''Currently the following tools are in pilot:'''
*Aurora design system

===Beta===
After Alpha testing has ended, the tool enters the Beta stage of development and testing. When in Beta the tool is at least 90% completed for the official release[https://www.softwaretestinghelp.com/beta-testing/]. The DCD uses open Beta testing to test its tools, meaning that the tool can be used and tested by every user in a real environment. 

During Beta testing users are asked to provide feedback on the design, functionality, and usability of the tool. Beta testing is also done to find minor bugs, as well as bugs which may have been missed in Alpha testing[https://www.softwaretestinghelp.com/beta-testing/].

Beta development uses the feedback provided by the real users to develop any additional enhancements to the features or design needed to release a tool which is usable with a positive user experience. Bug fixes are also applied during this stage. There may be multiple versions of Beta releases during this stage[https://techterms.com/definition/beta_software].

===Official Release===
When all necessary features and design are developed and implemented to the new tool, it is officially released. As the DCD works in an agile environment an official release does not mean that development on the tool ends. Further enhancements to the features are developed, and bug fixes are applied.