Digital Enablement Development Release Cycle

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.

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.

Minimal Viable Product (MVP) vs. Minimal Marketable Product (MM) 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. What is a minimal marketable product? The minimal marketable product (MMP) is a version of a product that includes a small set of features that addresses the needs of the initial users (innovators and early adopters), and that can be released to the market. The main goal of the MMP is to reduce the time-to-market as it can be launched more quickly than a feature-rich product. The MMP helps focuses on what really matters, without all the unnecessary features. In summary: The MVP helps you test your ideas. The MMP enables you to launch your product faster.

Pilot

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. A Pilot is sometimes referred to as Pre-Alpha.

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.

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.

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.

The following applications are in Pilot phase:

• Message

Alpha

Once an application (existing open source software or new MVP) successfully passes the pilot phase, the application will undergo Alpha development and testing. During this phase, the features and design of the application are developed based on the user feedback received during the Pilot phase.

If using an open-source application, DE will develop additional features and/or remove features in order to meet users' needs, and align the user interface to use the Aurora design system. The main focus is to make the application stable, accessible and usable for the user base.

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 that affect the functionality of the tool. The DE-D team also focuses on accessibility testing during this stage.

When in Alpha, the tool is functional but may not include all of the enhancements that will be part of the Minimal Marketable Product (MMP) and the official release. The Alpha phase is complete when all of the necessary features and design are developed and tested, and the tool is ready to be released as the MMP, during the Beta phase, to the entire user base for further testing and feedback.

The following applications are in Alpha phase:

• No application at this time.

Beta

After Alpha testing has ended, the application enters the Beta phase of development and testing. When in Beta, the application is at least 90% completed and is release to users as the Minimal Marketable Product (MMP). 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 and address minor bugs, as well as bugs that may have been missed in Alpha testing. The DE-D team uses open Beta testing to test its tools, meaning that the tool can be used and tested by every user who wishes to participate in testing in a real environment.

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.

The following tools are in Beta phase:

• Aurora design system

Official Release

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:

• GCaccount

• GCWiki

• GCcollab (legacy)
• GCconnex (legacy)
• GCpedia (legacy)