Comments on: Songbird path to Agility – Part I http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/ Play music. Play the Web. Sat, 20 Mar 2010 16:41:24 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: auberger.com http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-65008 auberger.com Thu, 12 Nov 2009 15:53:11 +0000 http://blog.songbirdnest.com/?p=411#comment-65008 <strong>Songbird path to Agility – Part I...</strong> This is a repost of a series of article originally published on Songbird's blog This is the first post of a 3 part series presenting our experience moving Songbird development to an Agile process. Drowning in the waterfall Up until version 0.3, Songb... Songbird path to Agility – Part I…

This is a repost of a series of article originally published on Songbird’s blog
This is the first post of a 3 part series presenting our experience moving Songbird development to an Agile process.
Drowning in the waterfall
Up until version 0.3, Songb…

]]> By: music player http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-46852 music player Wed, 11 Mar 2009 12:19:23 +0000 http://blog.songbirdnest.com/?p=411#comment-46852 Interesting read for sure. A little complicated for someone like me that just stumbled into this article searching Google. But I'll keep trying. Please keep posting more info. Interesting read for sure. A little complicated for someone like me that just stumbled into this article searching Google. But I’ll keep trying. Please keep posting more info.

]]> By: Dieresys » Blog Archive » Sobre agilidad, control de versiones y productividad http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-46513 Dieresys » Blog Archive » Sobre agilidad, control de versiones y productividad Sat, 07 Mar 2009 19:40:56 +0000 http://blog.songbirdnest.com/?p=411#comment-46513 [...] de Southplans, estuvimos inviestigando un poco sobre metodologías Ágiles. La gente de Songbird nos cuenta como se Agilizaron un poco. Sigo esperando al segunda parte. Tags: gnome, links, programacion, [...] [...] de Southplans, estuvimos inviestigando un poco sobre metodologías Ágiles. La gente de Songbird nos cuenta como se Agilizaron un poco. Sigo esperando al segunda parte. Tags: gnome, links, programacion, [...]

]]> By: Coding Notes » Welcome. http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-42805 Coding Notes » Welcome. Sun, 18 Jan 2009 02:33:51 +0000 http://blog.songbirdnest.com/?p=411#comment-42805 [...] out the first three parts of the “Songbird path to agility” series here: part i, part ii, part [...] [...] out the first three parts of the “Songbird path to agility” series here: part i, part ii, part [...]

]]> By: Process Automation http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-40792 Process Automation Wed, 24 Dec 2008 08:47:52 +0000 http://blog.songbirdnest.com/?p=411#comment-40792 Excellent Article. Thanks for the hard work and the valuable information for sharing with us. Excellent Article.

Thanks for the hard work and the valuable information for sharing with us.

]]> By: Georges Auberger http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-40180 Georges Auberger Wed, 17 Dec 2008 20:16:45 +0000 http://blog.songbirdnest.com/?p=411#comment-40180 @Jamie You are correct, that's the downside of choosing a linear scale. A Fibonacci or exponential scale http://en.wikipedia.org/wiki/Story_points can be more appropriate. In our case, we've been tracking the distribution of 1, 2 and 3 pointers across releases which seems to remain comparable. @Jamie

You are correct, that’s the downside of choosing a linear scale. A Fibonacci or exponential scale http://en.wikipedia.org/wiki/Story_points can be more appropriate. In our case, we’ve been tracking the distribution of 1, 2 and 3 pointers across releases which seems to remain comparable.

]]> By: Jamie Macey http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-40179 Jamie Macey Wed, 17 Dec 2008 19:36:51 +0000 http://blog.songbirdnest.com/?p=411#comment-40179 If your points aren't comparable, that makes your velocity and anything depending on it useless. If three 3 point stories wind up equivalent to twenty 1 point stories, Bad Things start to happen to your planning (either overestimating or underestimating, depending on if there's more of one group or the other). If your points aren’t comparable, that makes your velocity and anything depending on it useless. If three 3 point stories wind up equivalent to twenty 1 point stories, Bad Things start to happen to your planning (either overestimating or underestimating, depending on if there’s more of one group or the other).

]]> By: Songbird Blog » Songbird path to Agility - Part II http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-22593 Songbird Blog » Songbird path to Agility - Part II Thu, 04 Sep 2008 17:40:31 +0000 http://blog.songbirdnest.com/?p=411#comment-22593 [...] Previously, we’ve examined the new development practices that the Songbird team adopted to plan and track a release. Everyone on the team was very eager to put them to the test. Unfortunately, at the time, we were still in the middle of the 0.3 release cycle and new work could only be started once that release was completed. During the 0.3 release, everything was still treated as a bug, but in fact, many bugs were stories and tasks in disguise. We decided to apply some of the newly defined tracking principle to help us guide and finish the cycle, so we could start fresh with our next release as soon as possible. [...] [...] Previously, we’ve examined the new development practices that the Songbird team adopted to plan and track a release. Everyone on the team was very eager to put them to the test. Unfortunately, at the time, we were still in the middle of the 0.3 release cycle and new work could only be started once that release was completed. During the 0.3 release, everything was still treated as a bug, but in fact, many bugs were stories and tasks in disguise. We decided to apply some of the newly defined tracking principle to help us guide and finish the cycle, so we could start fresh with our next release as soon as possible. [...]

]]> By: Dieresys: Sobre agilidad, versioncontrolación y productividad http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-21704 Dieresys: Sobre agilidad, versioncontrolación y productividad Mon, 01 Sep 2008 17:44:30 +0000 http://blog.songbirdnest.com/?p=411#comment-21704 [...] de Southplans, estuvimos inviestigando un poco sobre metodologías Ágiles. La gente de Songbird nos cuenta como se Agilizaron un poco. Sigo esperando al segunda [...] [...] de Southplans, estuvimos inviestigando un poco sobre metodologías Ágiles. La gente de Songbird nos cuenta como se Agilizaron un poco. Sigo esperando al segunda [...]

]]> By: Lubos Mikusiak http://blog.songbirdnest.com/2008/06/25/songbird-path-to-agility-part-i/comment-page-1/#comment-18697 Lubos Mikusiak Tue, 12 Aug 2008 07:37:06 +0000 http://blog.songbirdnest.com/?p=411#comment-18697 Very interesting reading. Thanks for sharing your experience. TomTom HOME development team practices scrum quite rigorously for about half year. This really contributed to higher productivity and being able to deliver on time. We are much more rigorous in our time estimates. We estimate hours rather than story points. Not everyone find this ideal but it works for us pretty well. After the sprint estimation session, we sum up the estimated hours and compare them with the amount of available hours in the team. If there is more work than available hours, some functionality is dropped from the sprint. This approach works only if the requirements are “preprocessed” before the estimation session. High-level design is done before the sprint. Developers prepare before the estimation session and break down the high-level design into smaller pieces, which can be estimated. This minimizes the possibility that some part of work is forgotten. I look forward to your next articles. It would be interesting to see, for example, how you involve testers in the iterations and whether the development team got more self-organized. Very interesting reading. Thanks for sharing your experience. TomTom HOME development team practices scrum quite rigorously for about half year. This really contributed to higher productivity and being able to deliver on time.
We are much more rigorous in our time estimates. We estimate hours rather than story points. Not everyone find this ideal but it works for us pretty well. After the sprint estimation session, we sum up the estimated hours and compare them with the amount of available hours in the team. If there is more work than available hours, some functionality is dropped from the sprint.
This approach works only if the requirements are “preprocessed” before the estimation session. High-level design is done before the sprint. Developers prepare before the estimation session and break down the high-level design into smaller pieces, which can be estimated. This minimizes the possibility that some part of work is forgotten.
I look forward to your next articles. It would be interesting to see, for example, how you involve testers in the iterations and whether the development team got more self-organized.

]]>