Many of the Agile development practices are centered around human interactions. It’s only natural to ask the question: “How do you do Agile with a distributed team?”.
It is idealistic to think that team members will be together in the same location. The engineers might be working from home because the scrappy startup has no offices, or talent has to be found abroad because there is a shortage locally. Whatever the circumstances, it’s very likely that one or more member of the development team are going to be remote.
This is a repost of a series of article I originally published for Songbird.
This is a following post to the series on Agile development at Songbird. As covered previously, I’ve created in-house tools to help with the planning and tracking of our release trains. The tool works off of Bugzilla and extracts meaningful information for project tracking. As it was originally meant to periodically generate an email status, it became apparent that it was too static for daily project tracking needs.
This is a repost of a series of article I originally published for Songbird.
In the previous two installments of this series on Agile development at Songbird, I’ve covered our move from waterfall to Agile and provided an in-depth look at some actual release cycles. In this last post, I’m going to introduce a tool — which I gave the uninspiring name sdpbot — built internally to help facilitate the tracking of our releases.