Changes

The Canada School of Public Service (CSPS) Digital Innovation Solutions (DIS) team is always working on new products to support the mandate of the CSPS, the Digital Academy (DA) and the Government of Canda (GC). As DIS works on developing new applications, the team is continuously developing, testing and releasing enhancements and fixes throughout the development release cycle. There are four stages of development, testing and release for a new web application: Proof of Concept, Alpha, Beta and Official Release.  

The Canada School of Public Service (CSPS) Digital Innovation Solutions (DIS) team is always working on new products to support the mandate of the CSPS, the Digital Academy (DA) and the Government of Canada (GC). As DIS works on developing new applications, the team is continuously developing, testing and releasing enhancements and fixes throughout the development release cycle. There are four stages of development, testing and release for a new web application: Proof of Concept, Alpha, Beta and Official Release.  

During the proof of concept phase, DIS will attempt to demonstrate the feasibility of a concept or product to verify if it has the potential of being used. DIS 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, DIS will attempt to demonstrate the feasibility of a concept or product to verify if it has the potential of being used. DIS 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.  

'''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 DIS 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.

'''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 DIS 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 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), DIS 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), DIS will determine if there is a need to pivot, abandon or come up with a different solution.<br>

==Alpha==

==Alpha==

Beta development uses the feedback provided by real users to develop any additional enhancements or make any modifications to the user interface design needed in order to release an application that is usable and accessible, offering the best possible user experience. There may be multiple versions of the application released during the Beta phase<ref>“Beta Software.” ''Beta Software Definition'', 5 Apr. 2013, techterms.com/definition/beta_software.</ref>.

Beta development uses the feedback provided by real users to develop any additional enhancements or make any modifications to the user interface design needed in order to release an application that is usable and accessible, offering the best possible user experience. There may be multiple versions of the application released during the Beta phase<ref>“Beta Software.” ''Beta Software Definition'', 5 Apr. 2013, techterms.com/definition/beta_software.</ref>.

==Official Release==

==Official Release==