At Abilis, the project is first. For us success is delivering quality IT solutions that meet or exceed industry performance standards.
Abilis follows a proven, repeatable process that delivers results.
That is how it is to do business with Abilis.
Our teams pursue innovation in order to create efficiency and added value, not innovation for its own sake. This mindset drives results.
Efficiency within our teams provides a true alternative over in-house or off-shore development. This is a huge part of our competitive advantage.
Highly motivated, focused teams that collaborate and learn from each other’s experience are exceedingly productive.
This FPFS (Fixed Price, Flexible Scope) approach is a key factor in (IC)2 being able to provide the solutions that best fit our customers’ needs and budgets, even when many of those needs aren’t fully understood at the beginning of a project.
AGILE and Unified Process influences
(IC)2 draws heavily upon established AGILE and Unified Process software development methods and techniques, including continuous integration, pair-programming, test-driven development and domain-driven design.
(IC)2 projects are managed using a series of short iterations, with each iteration delivering value that is immediately pushed into the production environment. Iterative development helps customers reap benefits early in a project but, more critically, permits constant review and feedback from users and stakeholders to ensure the solution being developed stays fully aligned with business objectives. (IC)2 iterations also enforce constant quality checks, thus ensuring each addition to the solution gets built on top of a robust and fully tested foundation.
Throughout the lifecycle of each (IC)2 project, teams constantly assess and prioritize risks that could de-rail development or reduce the business value to the customer. During any iteration, the perceived higher priority risks are always tackled and mitigated, whether through development, prototyping or analysis.
Innovation Center tools and environment
(IC)2 projects are most effective when conducted from within one of Abilis’ North American Innovation Centers. The Centers provide an open and supportive environment through which teams, assembled together in pods, can collaborate face-to-face with minimal communication overhead. The secure development environments provide integrated tools to seamlessly manage requirements, design models, code, tasks, issues, risks, defects and test cases.
Planning for change
(IC)2 projects aren't just adaptable to change; they openly encourage and promote it. A project with static goals, static requirements and a static design will typically provide weak business returns. (IC)2 projects constantly look to improve on the initial goals, requirements and designs in order to give more value to the business. This is done through checkpoint meetings in each iterative cycle, but also by closely involving customers in project decisions and through the culture of ‘Just In Time’, whereby requirements and designs are crystallized at the last possible point.
No matter how good a new technology is, if it doesn’t make business sense, it’s not relevant. Aligning technology to business is the only way to maximize IT investment.
Abilis team remains agnostic in their technology choice. The best technology to tackle a business challenge. We are not a software reseller.