A Uniquely Agile Methodology

Iterative development is a core component of our strategic delivery approach. When you work with Aginity, you don't wait until the end of a project to for tangible, testable deliverables.

We divide each engagement into iterations that produce working versions of the product that our clients can actually use. Each iteration allows for client feedback and proactive "course corrections" to guarantee that the solution meets the original vision and business objectives and not just the technical spec.

• Each iteration begins with a debrief on the prior iteration and a planning and analysis session involving both the client and Aginity teams.
• A formal iteration review process is supplemented by the continuous delivery of functionality through weekly or daily builds, giving users ongoing access for testing and review.
• Major functional elements are grouped in formalized releases which represent critical project milestones.

Prototyping - Managing Risk, Increasing Efficiency

Aginity uses a special form of iteration called a Prototype Iteration, typically planned and executed at the start of a project, to explore unknown or the risky elements. This process allows us to address specific unknown issues aggressively and rapidly in order to ensure that we successfully clear project hurdles. Prototype Iterations help us to manage risk by isolating and focusing explicit efforts on high risk items.

Aggressive Testing Procedures

For Aginity, testing isn't merely an afterthought, it's integral to the entire development process.

From the beginning of a project we architect and plan in full view of business objectives while constantly testing these objectives against the reality of the user experience as well as technology realities and changes in the business universe.

Our strategic approach ensures that we have full and accurate use cases to drive our testing methodology and plans. We are not just testing what works, we are testing whether it delivers against the business model.

Additionally, we use a programming approach called Test Driven Development, which involves programming the unit test before we write the actual code. We employ a wide range of other practices designed to ensure quality including daily builds which ensure that the software component not only works on the developer's desk top, but integrates successfully into the total application before we consider it complete.