Changes

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

For the pilot phase, DE-D will either test the selected open source software to decide if it meets the initial requirements, or will test the newly developed product MVP and/or future releases, based on product requirements. The new tool will then enter the Alpha stage where the majority of the new development and design work for the new tool is completed. After all the initial 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.  

During the pilot phase, DE-D will either test the selected open source software to decide if it meets the initial requirements, or will test a newly developed product Minimal Viable Product (MVP). Once the application successfully passes the pilot phase, the application will then enter the Alpha phase where the majority of the new development and design work for the new application 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.  

  {| class="wikitable"

  {| class="wikitable"

|-

|-

|'''What is a minimal viable product?'''

|

In agile product development, the minimum viable product (MVP) is a bare-bones version of a new product that contains a minimum amount of features (usually 1 or 2) and that allows a team to get initial feedback from a small group of users with the least effort.<br><br>

 

==== '''What is a minimal viable product?''' ====

In agile product development, the minimum viable product (MVP) is a bare-bones version of a new product that contains a minimum amount of features (usually 1 or 2) and that allows a team to get initial feedback from a small group of users with the least effort

 

As the main goal of the MVP is to facilitate validated learning, it can take the form of paper prototypes and clickable prototypes that generate qualitative data (as opposed to quantitative data), as long as it helps to test the idea and to acquire the relevant knowledge.

As the main goal of the MVP is to facilitate validated learning, it can take the form of paper prototypes and clickable prototypes that generate qualitative data (as opposed to quantitative data), as long as it helps to test the idea and to acquire the relevant knowledge.

|}

|}

==Official Release==

==Official Release==

When all necessary features and design are developed and implemented to the new tool, it is officially released. As the DE 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 DE 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.

When all necessary features and designs are developed and implemented as part of the new application, it is ready to be officially released. As the DE-D team works in an agile environment, an official release does not mean that development on the application ends. User research is routinely conducted to determine if enhancements are reuqired  and how the usability of the tool can be improved. After the official release, DE-D continues to fix bugs, develop and release new features, enhancements and improvements on a continuous basis throughout the entire life-span of the application.

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

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

* [https://account.gccollab.ca/profile/ Account]

* [https://account.gccollab.ca/profile/ GCaccount]

* GCWiki

* GCWiki