To lock- in requirements before project development begins is the requirement of traditional software development methodologies. This approach is not quite feasible today, for change is inevitable and necessary in the requirements determining the delivery of technical assets.

In the agile world, change is expected and requirements are assigned to Time-boxes. The customers can add/remove/change requirements along with the team in a Time-box (essentially an iteration). Each such Time-box contains requirements that are created in a meeting at the start of the time-box. The customer can trade functionality in/out of this time-box, thereby enabling flexibility and mitigating risks. The project is thus divided into Time-boxes and working code is delivered quickly, in small iterations.

AGDF (Agile Global Delivery Framework) addresses those aspects of agile that fit best for a dispersed team. In specific, the additional skills and cost benefits that could be explored in a multishore project delivery model. It recommends best of breed processes & tools that could be used, along with the need for training that are required by distributed agile development and delivery.

The Agile alliance consists of 17 people representing 7 different methods, each of which differ in terms, parameters and concepts. Choosing the best method or a combination of them and suitably customizing it for your needs may be a bit tricky.

AGDF assists in identifying some of the best practices and methods to succeed with your distributed agile development. It discusses a few practical steps for a better project management and delivery, along with 11 best practices, 7 values and 5 steps.