The most important question that we at JAYA answer before starting on a project is:

What is the purpose of this application and why is it needed?

The answer to this question constitutes the business objectives of the project that should drive its entire lifecycle.

These business objectives drive the entire development process, and the requirements and design are continuously refined while the code evolves. The project plan arranges the development into small releases, and mandates continuing integration of all coded components, incremental builds, and periodic validation of refined requirements and design. By doing so, it encourages a shared ownership of the product among business analysts, software architects, designer, programmers, and testers; this shared ownership reduces the risk of miscommunication and divergence. It also enables continuing refinement and integration to avoid any unpleasant surprises just before the delivery date.

Our development methodologies aim to achieve the following:

• Quick feedback loop from business stakeholders to engineering back to business stakeholders
• Rapid software product conceptualization and materialization through prototyping
• Ability to refine requirements and design, and handle changes in both in the early phases of a product lifecycle
• Focus on getting the highest priority features and the highest risk features implemented as fast as possible
• Ability to validate pieces of design incrementally, providing continuous analysis and mitigating the risks