Delivery Model

Axioon has its own complete delivery and support model which is a specialized framework to manage end-to-end business engagement which comprises of Business Life Cycle Management (BLCM) and Product Life Cycle Management (PLCM). From the inception, we maintain a constant communication with our clients throughout the project with regular updates allowing them to experience how their business requirements are transformed into fully-fledged software solutions. Our process is open for adapting changing requirements and flexible enough to incorporate them into ongoing development cycles.

Agile practice

We are simply trying to deliver value, faster and earlier. Our agile teams deliver high value solutions to end users on a frequent basis (every couple of weeks). They build systems from end to end, instead of layer on layer to provide useful, demonstrable functions earlier than later. They use richer forms of communication favoring conversations over just passing documents back and forth, and building in numerous feedback loops to continually steer a project to success. They raise visibilities into issues earlier based on real data about how the project is being built instead of relative to a plan developed at the very start of a project. By looking at all the dimensions required to deliver software early they uncover risks otherwise found much later in a project's lifetime. Fact-based information gives investors a more powerful set of choices to decide upon instead of simply hoping for the best.

Some of the principles behind the agile development are:

  • Customer satisfaction is achieved by the rapid, continuous delivery of useful software.
  • Working software is delivered frequently (weeks rather than months).
  • Working software is the principal measure of progress.
  • Even late changes in requirements are welcome (this does not mean "code and run." Instead, it means removing an existing feature or moving a deadline forward to accommodate late or unplanned feature requests).
  • Close daily cooperation between business and development groups.
  • Face-to-face conversation is considered the best form of communication (Co-location).
  • Projects are built around motivated, trustworthy individuals.
  • Continuous attention to technical excellence and good design.
  • Simplicity.
  • Self-organizing teams.
  • Regular adaptation to changing circumstances.

Quality practice

Quality Assurance both at product and processes levels is given a key importance at Axioon. Our proprietary Quality Management System provides a flexible process framework that enables continuous quality improvement.

Axioon execution is based on the Iterative Development methodology. For each particular iteration quality control analysts are involved in the following activities: 

  • Requirements analysis – defining the acceptance criteria and product performance requirements for the iteration.
  • Test strategy creation – manual and automated testing approach, tools, environment and functionality to be tested
  • Iteration planning – creation of the test plan and test cases.
  • Testing – conducting integration, system (functional, installation, recovery, performance, load, and compatibility tests), regression, and acceptance testing of the product based on the functional requirements and test cases.
  • Defect management – defect lifecycle, defect verification, defect trends analysis.
  • Acceptance – product validation according to the defined acceptance criteria and reporting.
  • Evaluation of test results – a QC release statement is prepared with recommendations for the release, as well as a detailed release report.