image description
contact us
Name* Phone* E-mail* Message*


Models: Agile Approach

Auriga is a global company that delivers a range of software development services, both through its Dedicated Development Centers (DDC) and through its Project Services, using various engineering methodologies. We are experienced with the increasingly popular family of Agile methodologies and possess expertise in the best practices and effective implementation of these methodologies. A wide range of engagement models, with Remote Engineering Center (REC) as its unbeaten champion for product companies, allows choosing the most suitable approach for the task in hand. We see the medium size of our company as our benefit, allowing us to provide the same high level of attention to all teams regardless of their size and to focus on interaction and communication that are critical to the agile approach.

Over the past several years Auriga has been doing projects that require evolutionary change throughout the entire life-cycle of the project with increasing frequency. The majority of our teams working for our customers—software and hardware high-tech companies—commonly use agile methods when developing new products, as requirements are developed, detailed, and changed as the project goes forward.

The development methodologies used by Auriga with different clients are not always formally called Extreme Programming, Scrum, or bear some other well-known formal name, but in fact employ all essential agile practices from classical methodologies. Part of the reason is that we always tailor the processes to match the specifics of the customer’s operation. Another part is that pure classical agile models need to be revised to a certain extent to be successfully applied to a “distributed agile” case, when in addition to the project team and the customer representative that cares about requirements, priorities, and acceptance, we have the internal engineering team on the customer’s side that needs to be included in the equation.

Typically, the following practices are used:

  • Short iterations with fixed scope
  • Continuous involvement of the customer
  • Direct communications at all levels
  • Frequent light-weight reviews
  • Test-driven development
  • Peer reviews and peer work, collective code ownership
  • Getting commitment from engineers through involvement in effort estimation
  • History-based planning & estimations
  • Strict up-to-date KISS principle in design, refactoring

Selected Auriga engineers have undergone training in agile methodologies. Therefore, Auriga can follow Agile agile methodologies both strictly as defined and informally, using the general agile principles.