Release Notes

<< Click to Display Table of Contents >>

Navigation:  Introduction >

Release Notes

This is version .


Version 2.1

Version 2.1 continues in the vein of the 2.0 releases and introduces a number of new interactive features which deliver significant incremental value to members including:


1.New Progress wheels allowing members to track and run through the options based on their plan

2.New Security meaning you only see what's relevant for your subscription model

3.Integration of new member database so we can assist members with exactly what they need.


The following are changes in this release:

New Task Wheels

New Guidance Email System

New Data Sources and Integration Packs

Better Mobile Support

Registered Members have 30 day free trial

New News system integrated with CRM

New Security Systems

New Community Pages and Integration

New Blog Platform

Added new Training and ANZ Education Library

New Amendments to the Waffle Menu


Version 2.0

Version 2.0 is a significant release from previous editions, meaning we updated the major release number. This release has a number of highlights including:


1.Brand new Public website introducing ASI Kairos to the members who have not registered.

2.New Pricing Models and Plans

3.New Activities and tracking system when using the portal

4.New Homepage

5.New Navigation and significant content additions


The following are changes in this release

New Homepage designed, and implemented

Central Database of Uses, members, registration and more produced

New and amended sales planning, flow and process based on member feedback

Meet the team updated to introduce new team members

New Portal and Public Website Information Architecture

Added ASI Kairos Store to Public Website

New Pages showing how to get started and use the Connected Practice and Predictive Accountant

Brand new 3 tier navigation menus

Addition of News and yammer to the home page

Implementation of new Pricing Page

Implementation of new Custom Pricing Page

Addition and configuration of new Central Database

Implementation of new Thank You Page

New Office 365 Descriptions

New Index and Searching

New Nurture Program and ongoing training communications

Integration of Dynamics 365 with ASI Kairos Portal

Largest and most extensive testing of the platform to date.


Internal Version 1.8

Changes in This Release

Registration Journey Defined

Subscriber Journey Defined

Portal Page Permissions Implemented

Portal Analytics Implemented

Numerous minor updates


Internal Version 1.6

Changes in This Release

ASI Kairos Bot Connector Defined

Dashboard Specifications Released

Wheel Diagram Released

Connected Practice

oPresentation on Microsoft Products and Services Created

oWorking Example for Client Churn Developed

Partner Program

oPartner Strategy Created


oMinor Cosmetic Updates


oBase Data Dictionary Documented


oAdditional Reporting Created



Release To Manufacturing (RTM) Version

Changes in this Release

Release Process

oCreate Launch EDMs

oCreate "Getting Started" Copy

oCreate Internal Digital Workplace Pages

oEnable Customer Service Center

oPPC Presentations

oNZ Tour


oComplete Explainer Videos

oComplete Video Vignettes

oImplement Inspectlets

oRedesign Contact Page

oCreate Pricing Section and Comparison Chart

oAdd Partner Companies

oBrand Approved Images

oCreate Using PowerBI Page


oComplete Execution of Various Agreements


oComplete and Release "Systems of Insight" Training


oComplete "Sales Kit"




A word on version  numbering:

             In our development process (MSF for Agile 6.0), we version as follows: ( where AA is the major version number. CA Karios release will be 4.2. bb is the minor version number which gets incremented each release unless a major rewrite occurs. Cccc is the build number and increases everytime we compile the solution.


Release version will be and all components will adhere to that numbering on release.


All the below is tracked in visual studio online:


A word on the software release cycle

For more information:



Pre-alpha refers to all activities performed during the software project before testing. These activities can include requirements analysis, software design, software development, and unit testing. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the functionality is complete.



The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white-box techniques. Additional validation is then performed using black-box or gray-box techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.[1]


Alpha software can be unstable and could cause crashes or data loss. Alpha software may not contain all of the features that are planned for the final version. In general, external availability of alpha software is uncommon in proprietary software, while open source software often has publicly available alpha versions. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete.



Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. Software in the beta stage is also known as betaware.[2] Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, preview release, prototype, technical preview / technology preview (TP),[3] or early access. Some software is kept in perpetual beta, where new features and functionality are continually added to the software without establishing a firm "final" release.


Beta testers are people who actively report issues of beta software. They are usually customers or representatives of prospective customers of the organization that develops the software. Beta testers tend to volunteer their services free of charge but often receive versions of the product they test, discounts on the release version, or other incentives.


As the Internet has facilitated rapid and inexpensive distribution of software, companies have begun to take a looser approach to use of the word "beta".[4] In February 2005, ZDNet published an article about the recent phenomenon of a beta version often staying for years and being used as if it were in production level, disparagingly called "perpetual beta". It noted that Gmail and Google News, for example, had been in beta for a long period of time and were not expected to drop the beta status despite the fact that they were widely used; however, Google News did leave beta in January 2006, followed by Google Apps, including Gmail, in July 2009.[5] This technique may allow a developer to delay offering full support and responsibility for remaining issues. In the context of Web 2.0, people even talk of perpetual betas to signify that some software is meant to stay in beta state. Also, "beta" is sometimes used to indicate something more like a release candidate, or as a form of time-limited demo, or marketing technique.[6]


Release candidate

A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bugs. A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities. Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product. Beta testing is conducted in a client's or customer's location and to test the software from a user's perspective.



Once released, the software is generally known as a "stable release". The formal term often depends on the method of release: physical media, on-line release or a web application.


Release to manufacturing (RTM)

The term "release to manufacturing", also known as "going gold", is a term used when a software product is ready to be delivered or provided to the customer. This build may be digitally signed, allowing the end user to verify the integrity and authenticity of the software purchase. A copy of the RTM build known as the "gold master" or GM is sent for mass duplication. RTM precedes general availability (GA), when the product is released to the public.


It is typically used in certain retail mass-production software contexts—as opposed to a specialized software production or project in a commercial or government production and distribution—where the software is sold as part of a bundle in a related computer hardware sale and typically where the software and related hardware is ultimately to be available and sold on mass/public basis at retail stores to indicate that the software has met a defined quality level and is ready for mass retail distribution. RTM could also mean in other contexts that the software has been delivered or released to a client or customer for installation or distribution to the related hardware end user computers or machines. The term does not define the delivery mechanism or volume; it only states that the quality is sufficient for mass distribution. The deliverable from the engineering organization is frequently in the form of a golden master media used for duplication or to produce the image for the web.


General availability (GA)

Milestones in a product life cycle: general availability (GA), end of life announcement (EOLA), last order date (LOD), and end-of-life (EOL)

General availability (GA) is the marketing stage at which all necessary commercialization activities have been completed and a software product is available for purchase, depending, however, on language, region, electronic vs. media availability.[10] Commercialization activities could include security and compliance tests, as well as localization and worldwide availability. The time between RTM and GA can be from a week to months in some cases before a generally available release can be declared because of the time needed to complete all commercialization activities required by GA. At this stage, the software has "gone live".


Release to web (RTW)

Release to web (RTW) or web release is a means of software delivery that utilizes the Internet for distribution. No physical media are produced in this type of release mechanism by the manufacturer. Web releases are becoming more common as Internet usage grows.



ASI Kairos Version History (Reverse Chronological)

4.2.220.RC1 (Release Candidate 1

Approved Release Candidate

Public Presentations

oCreated Public Presentation Set

oCreated ASI Kairos Promo Video Playlist

oTrained RM Staff

oTrained Service Center

oBuilt Team Surface Books

oCustomer Service Script

oEmail Address AutoResponder

oCA ANZ HomePage Content Submitted

oBeta Customers Invited to Register


oInstigated Portal Analytics

oChanged Design to Mobile Friendly Responsive Design

oCreated Meet the Team Page

oSite Sign Off

oUpdate DNS Entries

oCreate Test Plan

Documentation Library

oVersioning Automation

oData Models User Guide

oPortal User Guides


oPrivacy Policy Review

oLiability Review

Production Implementation

oApproved Rhipe Partner Program

oApproved Support Service Levels

oCompleted Provisioning Documentation


oExternal Comms Strategy

oTrain BDEs

Integration Packs

oPractice Data

oChurn Predictor

oBusiness Segmentation


oProduction & Lodgement

oClient Churn

oClient Acquisition

oPractice Health

oCustomer Segmentation

oBusiness Systems Review

oPlan My Business

oExplainer Video for Client Churn

oExplainer Video for Client Acquisition

oExplainer Video for Practice Health

oExplainer Video for Plan my Business

oExplainer Video for Business Systems Review


oChanged Explainer Video Audio

oCreated Production and Lodgement Explainer Video



Approved Beta Release

Implemented Yammer List, Welcomed Participants to Portal

Created Explainer Videos


oCompleted Commercial Negotiations with providers

oUpdated Terms and Conditions

oIncluded all relevant Microsoft EULA Agreements

Integration Packs

oAdded Australia and New Zealand Regulatory Calendar

oCommenced Practice Data and enhanced existing packs

oCommenced Client Churn


oCommenced Production and Lodgement

oCompleted Seeing Patters

oAgreed final scenario list


oCompleted Portal IA

oRevised Header and Footer

oMoved Portal to new home

oConsolidated Home Page

oCreated and Defined Wizards

oCreated Huge Resources Section

oEnabled Registration

oEnabled and documented Security

oApplied Certificates

oCreated Site Admin Guide

oAdded TCP Explainer Video

oUpdated Main Nav

oWrote Video Filename Schema

Documentation Library

oUpdated Sales Kit

oCreated new schedules

oAdded Work orders

oAdded TPA. TCP and Speedway info

oCompleted Member handbook

oCompleted Builds

oFinalised Frameworks

oCompleted Glossary

oCompleted Knowledge base

Data Sources

oCompleted XPM

oCompleted Excel Models

oCompleted ANZ Truckometer

oCompleted CIA World Factbook

oCompleted Google

oCompleted Petrol Spy Australia

oCompleted Core Infrastructure

oCompelted Bing






Approved Alpha Release

Added Sales Kit -> Brochure

Added Sales Kit -> Elevator Pitch

Added Sales Kit -> Data Sheet

Added Landing Site

Added Client Invoice Integration Pack

Added Xero QI Integration Pack

Added QuickBooks Online QUI Integration Pack

Added Seeing Patterns Scenario

Added New Portal inline with Brand Requirements

Added Wizard Concept

Added Release Notes (this document)

Added Portal User Guide

Added TCP Documentation

Added Partner DOcumentation

Refined Deliverables

Documented PowerShell Libraries

Added Content to Introduction

Documented All Scenarions

Added Sales Kit -> Overview

Added Sales Kit - Presentation

Added Sales Kit -> Proposal Template

Added Sales Kit -> Battlecard

Created 2x Explainer Videos

Added Excel Connector

Documented KB -> Connected Practice

Documented KB -> Office 365



Added Glossary of Terms

Added Knowledgebase and FAQ

Added Automated Build System




Highlights of this release are:


Xero Practice Manager Data Source 1.0 (Export) Released

Xero Practice Manager Data Source 0.9 (API) in Beta

Xero Practice Manager Integration Pack 0.9 (All) in Beta

Portal Design Finalised, Production Portal well underway


Additional Work completed:



Connected Practice Documentation Library well underway:

             Introduction – Complete

             Connected Practice Portal – In Progress

             Connected Practice – Complete

             Predictive Accountant – In Progress

             Partner Program – Complete

             KIE – Technical Guide Complete, Script in Progress

Beta Program – Meeting with Initial clients in play

Data Dictionary – Complete

Practice Manager Data Models In Beta


             Xero Practice Manager

             MYOB AE

             Reckon APS

             Reckon Elite

Connected Practice Components Released

             Template Manager

             Migration Manager

             Mail Template Manager

             Mail Manager

             Scanned Document Manager

Predictive Accountant Data Sources Complete




             ANZ Truckometer

             Petrol Spy


             CIA World Factbook

Connected Practice Architecture Defined.

Legals – License Agreements Released. Business Models and Pricing well progressed