Anahata uses Agile as software development methodology.
In Agile methodology, all project participants (including the customer) work closely to deliver the requirements in line with the customer’s expectation. To achieve this, good communication is required between the customer and the engineers.
To ensure a project or a set of tasks are delivered in the most efficient possible way, frequent meetings and checkpoints may be required between the customer and the engineers. This can take the form of video conferences, e-mail conversations, phone conversations or face to face meetings.
As mutually agreed, checkpoints can be set regularly (e.g. daily or bi-weekly), on an ad-hoc basis, or both.
The development process is a continuous repetition of the following stages which are repeated in the form of iterations, the length of an iteration can vary depending on the size and the complexity of the goals set for a given iteration.
The first stage of the process is the requirements gathering, where software engineers liaise with the customer as to understand what the business requirements are.
The second stage of the process starts once a set of requirements has been understood and the engineers work on the application or tasks to be developed. During this process, regular checkpoints and feedback with the client may be required to clarify requirements and ensure the development conducted aligns with the customer’s expectations.
This stage is the testing stage, during this stage, the application will be deployed to a test environment, where the customer can test the application or changes requested. The test environment is provided by Anahata and there is no charge for it.
If during the testing, defects are detected or necessary changes are identified, the process will continue again on stages 1 or 2 to address the encountered defects or requested changes.
If the testing is successful, the customer shall sign off on the test release and the application will be deployed to production.
During this stage, the application will be deployed to production. To deploy an application or a new version of an application to production, a system outage is generally required.
Production outage as part of a production implementation is optimistically of around 2-5 minutes but can become longer if issues were encountered.