Comments on: My experiences with distributed Agile software development http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/ Thu, 18 Mar 2010 13:27:36 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: David http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-56205 David Fri, 10 Oct 2008 21:14:26 +0000 http://blog.xebia.com/?p=701#comment-56205 Nice read. I would disagree with the comment that it takes 6 months for a new to Agile developer to contribute to the team, we have seen developers contribute in the first few weeks - but I do believe some developers can work in Agile and some can't based on personality. Nice read. I would disagree with the comment that it takes 6 months for a new to Agile developer to contribute to the team, we have seen developers contribute in the first few weeks – but I do believe some developers can work in Agile and some can’t based on personality.

]]> By: Tommy D http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-53201 Tommy D Thu, 11 Sep 2008 10:42:24 +0000 http://blog.xebia.com/?p=701#comment-53201 A comprehensive post is very useful for those who needs information about distributed development system, thanks.. for sharing this. A comprehensive post is very useful for those who needs information about distributed development system, thanks.. for sharing this.

]]> By: Case study: Distributed Scrum Project for Dutch Railways | Xebia Blog http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-50358 Case study: Distributed Scrum Project for Dutch Railways | Xebia Blog Mon, 18 Aug 2008 06:13:04 +0000 http://blog.xebia.com/?p=701#comment-50358 [...] Mulder in the early morning: August 18, 2008 Recently I wrote a blog about the way that we do distributed Agile projects. Martin van Vliet and I have also published an article on InfoQ about one of them. So if you want [...] [...] Mulder in the early morning: August 18, 2008 Recently I wrote a blog about the way that we do distributed Agile projects. Martin van Vliet and I have also published an article on InfoQ about one of them. So if you want [...]

]]> By: Marco Mulder http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-49992 Marco Mulder Thu, 14 Aug 2008 08:18:31 +0000 http://blog.xebia.com/?p=701#comment-49992 Hi Shrikant. That is a very interesting case. I think that a description of experiences on this project deserves it's own blog! Hi Shrikant. That is a very interesting case. I think that a description of experiences on this project deserves it’s own blog!

]]> By: ShriKant Vashishtha http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-49986 ShriKant Vashishtha Thu, 14 Aug 2008 07:13:43 +0000 http://blog.xebia.com/?p=701#comment-49986 The problem is even deeper when you are working in different timezones having 12 hours of time-difference. Finding the overlapping between two teams becomes even more difficult. In that scenario, it requires a bit of adjustment from both sides. Sometimes one team comes a little early and sometimes other team. Instead of the whole team of one side staying late, people rotate at the time distributed standup and stuff like that. Once in a week both teams stay together. The most important task is to have as much as communication as possible which may include initially collacating team as mentioned in the blog. Xebia India executed one such distributed project successfully. The problem is even deeper when you are working in different timezones having 12 hours of time-difference. Finding the overlapping between two teams becomes even more difficult. In that scenario, it requires a bit of adjustment from both sides. Sometimes one team comes a little early and sometimes other team. Instead of the whole team of one side staying late, people rotate at the time distributed standup and stuff like that. Once in a week both teams stay together. The most important task is to have as much as communication as possible which may include initially collacating team as mentioned in the blog. Xebia India executed one such distributed project successfully.

]]> By: Anurag http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-49978 Anurag Thu, 14 Aug 2008 05:07:50 +0000 http://blog.xebia.com/?p=701#comment-49978 Good post... it takes six month before a new joiner can contribute in an Agile team if he was not exposed to the right kind 'Agile' before... Good post… it takes six month before a new joiner can contribute in an Agile team if he was not exposed to the right kind ‘Agile’ before…

]]> By: Abhishek http://blog.xebia.com/2008/08/13/my-experiences-with-distributed-agile-software-development/comment-page-1/#comment-49974 Abhishek Thu, 14 Aug 2008 04:54:51 +0000 http://blog.xebia.com/?p=701#comment-49974 Excellent blog. You captured the essence of it all very nicely. I personally believe the above 5 points are absolutely necessary for any distributed development effort to be successful. Excellent blog. You captured the essence of it all very nicely.

I personally believe the above 5 points are absolutely necessary for any distributed development effort to be successful.

]]>