Changes

The Digital Enablement Development (DE-D) Division 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 web application: Pilot, Alpha, Beta and Official release.  

The Digital Enablement Development (DE-D) Division 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 web application: Pilot, Alpha, Beta and Official release.  

Before entering the development process, DE-D will determine if an existing open source software exists that meet the business, technical and user requirements for the application. If none meet the requirements, DE-D will look into developing the new application, starting with an minimal viable product (MVP) where they will continue to iterate on the application to add additional features and functionalities.   

Before entering the development process, DE-D will determine if an open source software exists that meet the business, technical and user requirements for the application. If none meet the requirements, DE-D will look into developing the new application, starting with an minimal viable product (MVP) where they will continue to iterate on the application to add additional features and functionalities.   

During the proof of concept phase, DE-D will attempt to demonstrate the feasibility of a concept or product to verify if it has the potential of being used. DE-D will either test an open source software to see if it meets the initial requirements, or will test a newly developed Minimal Viable Product (MVP). If the concept or product successfully goes through the proof of concept phase, it will then enter the Alpha phase where the majority of the new development and design work for the new product will be completed. Once the initial necessary features are developed and tested in Alpha, the new tool will enter the Beta phase where at least 90% of the application is completed and is released to users as the Minimal Marketable Product (MMP). During the Beta phase, final bug fixes and enhancements required are addressed before the application is officially released.  

During the proof of concept phase, DE-D will attempt to demonstrate the feasibility of a concept or product to verify if it has the potential of being used. DE-D will either test an open source software to see if it meets the initial requirements, or will test a newly developed Minimal Viable Product (MVP). If the concept or product successfully goes through the proof of concept phase, it will then enter the Alpha phase where the majority of the new development and design work for the new product will be completed. Once the initial necessary features are developed and tested in Alpha, the new tool will enter the Beta phase where at least 90% of the application is completed and is released to users as the Minimal Marketable Product (MMP). During the Beta phase, final bug fixes and enhancements required are addressed before the application is officially released.  

|}

|}

==Pilot==

==Proof of Concept==

DE may test multiple open-source applications to develop a particular tool. When a tool is in the Pilot phase, it means that an open-source application or a '''Minimal Viable Product (MVP)''' is being tested to see if it can meet the user needs, and business and technical requirements, before the tool undergoes more comprehensive development by the DE-D 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> A 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>

A proof of concept (POC) is a way for DE to test and demonstrate the feasibility of a concept or product to verify if it has the potential of being used. A proof of concept is usually small and may or may not be complete. DE-D will either test an existing open source application to see if it meets the initial requirements, or will test a newly developed '''Minimal Viable Product (MVP)''', before the product undergoes more comprehensive development by the DE-D team. It is a short-term, experimental phase to see how the large-scale service may work in practice and allows to better investigate a set of technologies and how they might work in a specific business culture.

Before launching a pilot application. the scope of the project is developed, including user, business and technical requirements. User requirements are determined through research, testing and analysis of the user base. From the project scope, the DE-D team defines a Minimum Viable Product (MVP) to be developed and launched as a pilot. The MVP will not include all the features planned for the application, only the minimum amount of features required to get initial feedback from users. Further features and enhancements which add value to the tool will be developed if the application successfully passes the pilot phase.  

Before doing a proof of concept, the scope of the project is developed, including user, business and technical requirements. User requirements are determined through research, testing and analysis of the user base. From the project scope, the DE-D team will conduct research to determine if an open source application exist that could meet these requirements. If not, DE-D will develop a Minimum Viable Product (MVP). The MVP will not include all the features planned for the application, only the minimum amount of features required to get initial feedback from users. Further features and enhancements that add value to the tool will be developed if the proof of concept proves to be successful.

'''Open Pilot testing''' means that the 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 DE-D 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 provides for more in-dept user feedback.

'''Open Proof of Concept''' means that the product, or application, is available and open for any users to test. '''Closed Proof of Concept''' means that the product, or application, is only made available to a small set of users, or is only available to the team who is developing the tool. The DE-D team uses both of these testing methods depending on what makes the most sense for the product being developed. When possible, open proof of concept is preferred as it includes the user at the earliest stage of development and provides for more in-dept user feedback.

If the MVP or open-source application being tested is deemed to successful, the application will go on to the next phase of development. If it is deemed to be unsuitable (e.g. does not meet user and/or business requirements), DE-D will determine if there is a need to pivot, abandon or come up with a different solution.  

If the MVP or open-source application being tested is deemed to be successful, the application will go on to the next phase of development. If it is deemed to be unsuitable (e.g. does not meet user and/or business requirements), DE-D will determine if there is a need to pivot, abandon or come up with a different solution.  

'''The following applications are in Pilot phase:'''

'''The following product is an open proof of concept:'''

*[https://message.gccollab.ca Message]

*[https://message.gccollab.ca Message]