News & Events About Xebia
India > Our Offering > Software Development > Agile Offshore > Process

Process

Embracing the change

Print
RSS feeds

Agile Software Development process is best suited to new application development projects where the detailed requirements are unclear or likely to change with time. Agile model applies timeboxed iterative and evolutionary development, adaptive planning, promotes evolutionary delivery, and includes other values and practices that encourage agility – rapid and flexible response to change.


Process to Respond to Change

Key benefits of the Agile delivery model lies in its ability to respond to business change and therefore it is particularly suited to the development of internet based applications or new application development. After several iterations the requirements of customer and the developed software converge to form a solution that meets customer’s expectations, works and meets the latest business needs.

 

Agile software development project begins with a set of high level requirements. A project is divided into three or more iterations of variable durations. Duration of iteration can vary between two to five weeks in the during the project. Customer chooses the requirements to be implemented at the start of iteration based upon their business value or technology risk. These requirements are implemented in a timeboxed iteration. At the end of iteration, team and customer feedback is used to take corrective actions and improve the estimations of the next iterations.

 


Process Steps


The following picture describes the steps in a typical Xebia Agile offshore project. In each step onsite and offshore teams remain involved, however the physical location and the size of the team may vary.

Click the picture to enlarge it.

 

An assignment starts with initial estimation which is done by an onsite consultant supported by an offshore team member in India. This is followed by two or three iterations onsite that take place onsite together with a mixed team of India and local programmers. The motivation behind the onsite iteration is to establish trust between the customer and the development team about team’s speed and ability to deliver, and tackle major risks early in the project.

After a successful completion of two and three iterations, the offshore team is scaled up and high productivity is achieved by deploying more resources in India.

After the the end of an iteration working software is delivered to customer. The customer tests working software in demo or test environment and provides feedback. In all iterations, whether carried out onsite or offshore, customer feedback and priorities act as the main drivers to determine the scope of next iteration.

Once no more requirements are left for development, the developed software is sent to the customer for the user acceptance testing. Offshore team remains stand by to support the UAT process.