Distributed Agile Delivery
Traditional software development methodologies mandate that requirements of the project be frozen
(locked-in) before the design and development activities commence. This approach may not be or is not
feasible today, for change is inevitable and necessary in the requirements determining the production 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 aspects of agile that would take on new significance in a dispersed team, specifically,
the additional skills and cost benefits that could be explored in multishore project delivery. It
recommends best of breed processes & tools that could be used, along with training needs and skills
for a distributed agile development 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.
This model ensures a high return-on-investment for the client and a dedicated team focused entirely on the client's projects.
»
more