Changes

{{Translation to follow}}

{{Translation to follow}}

The Digital Collaboration Division (DCD) continuously develops, tests and releases enhancements and fixes for its applications throughout their life cycle. There are four stages of development, testing and release for a new DCD application: Pilot, Alpha, Beta and Official release.  

The Digital Collaboration Division (DCD) continuously develops, tests and releases enhancements and fixes for its tools throughout their life cycle. There are four stages of development, testing and release for a new DCD tool: Pilot, Alpha, Beta and Official release.  

First an application will be in Pilot to determine what open-source software the new application will be using, or if it will be built from scratch. Once an open-source software is selected or a decision has been made to build from scratch, the new application will enter the Alpha stage where the majority of the new development and design work for the new application is completed. After all of the necessary features are developed and tested in Alpha, the new application will enter the Beta stage for any final bug fixes and enhancements required before the Official release.  

First a tool will be in Pilot to determine what open-source software the new tool will be using, or if it will be built from scratch. Once an open-source software is selected or a decision has been made to build from scratch, the new tool will enter the Alpha stage where the majority of the new development and design work for the new tool is completed. After all of the necessary features are developed and tested in Alpha, the new tool will enter the Beta stage for any final bug fixes and enhancements required before the Official release.  

==Pilot==

==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 user needs, and business and technical requirements, 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.<ref>Rouse, Margaret''. “What Is Pilot Program (Pilot Study)? - Definition from WhatIs.com.”'' SearchCIO, June 2013, searchcio.techtarget.com/definition/pilot-program-pilot-study.</ref> Pilot is sometimes referred to as Pre-Alpha.<ref>“Software Release Life Cycle.” ''Wikipedia'', Wikimedia Foundation, 7 Oct. 2018, en.wikipedia.org/wiki/Software_release_life_cycle#Pre-alpha.</ref>  

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 user needs, and business and technical requirements, 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.<ref>Rouse, Margaret''. “What Is Pilot Program (Pilot Study)? - Definition from WhatIs.com.”'' SearchCIO, June 2013, searchcio.techtarget.com/definition/pilot-program-pilot-study.</ref> Pilot is sometimes referred to as Pre-Alpha.<ref>“Software Release Life Cycle.” ''Wikipedia'', Wikimedia Foundation, 7 Oct. 2018, en.wikipedia.org/wiki/Software_release_life_cycle#Pre-alpha.</ref>  

During this stage, the scope of the project is developed, including user needs, business and technical requirements. User requirements are determined through research, testing and analysis of our user base. From the project scope, the DCD team defines a Minimum Viable Product (MVP) to be developed for an Official release. The MVP will not have every feature planned for the application, only the features required to make the application valuable for the user and business. Further features and enhancements which add value to the application will be developed after the Official release.  

During this stage, the scope of the project is developed, including user needs, business and technical requirements. User requirements are determined through research, testing and analysis of our user base. From the project scope, the DCD team defines a Minimum Viable Product (MVP) to be developed for an Official release. The MVP will not have every feature planned for the tool, only the features required to make the tool valuable for the user and business. Further features and enhancements which add value to the tool will be developed after the Official release.  

'''Open Pilot testing''' means that the potential open-source application is available for real users 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 being developed. 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.

'''Open Pilot testing''' means that the potential open-source application is available for real users 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 being developed. 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.

==Official Release==

==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, support is provided, and bug fixes are applied throughout the entire life of a tool.

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. User research is routinely conducted to see which new features will enhance the tool and how the usability of the tool can be improved. After Official release DCD continues to develop and apply these features, enhancements and improvements. Additionally support is provided, and bug fixes are applied throughout the entire life of a tool.

'''The following tools have been Officially released:'''

'''The following tools have been Officially released:'''