Some distributed Agile development were a real success. For instance........ Eclipse.
The Eclipse team has created a process based on Agile, called The Eclipse Way
It is usually admitted that the more you need formalism, the more your process must be robust
Depending on your needs, you can adopt (and adapt) 3 different processes all based on Agile. - OpenUP (small collocated teams) - Eclipse Way (distributed teams, low level of formalism) - RUP (distributed teams, traceability, high ceremony)
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
Originally posted by Pradip Bhat: I am felling that agile development does not work if the team is geographically located. The team may have to attend meetings at weird times many time a week.
The point is that a team needs to communicate. If they can't meet at least once a day, the project will suffer, Agile or not.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Bring me the box labeled "thinking cap" ... and then read this tiny ad: