Re: [Analytics] Team's Sprint Commitments

2014-07-15 Thread Kevin Leduc
Hi Pierre-Selim Before the last sprint, we adjusted how many points we assign to stories. We didn't have enough range to compare the complexity, and all things ended up being 5, 8 or 13 points. This was identified at a retrospective so we decided to recalibrate our points scale. Therefore it's

Re: [Analytics] Team's Sprint Commitments

2014-07-15 Thread Pierre-Selim
Just out of curiosity (as a product owner myself), as I can see the team is planning and delivering more and more at each sprint 16, 31, 45 and 55 (current sprint): is there any reason for such increase in velocity ? Oh btw kudos for all the features delivered, and thank you for the transparency w

Re: [Analytics] Team's Sprint Commitments

2014-07-15 Thread Christian Aistleitner
Hi, On Wed, Jul 02, 2014 at 11:00:44AM +0200, Christian Aistleitner wrote: > On Tue, Jul 01, 2014 at 09:16:26AM -0700, Kevin Leduc wrote: > > Our current sprint started Thursday June 26 and ends Tuesday July 8th. > > [...] > > http://sb.wmflabs.org/t/analytics-developers/2014-06-26/ Of the origin

Re: [Analytics] Team's Sprint Commitments

2014-07-02 Thread Christian Aistleitner
Hi, On Tue, Jul 01, 2014 at 09:16:26AM -0700, Kevin Leduc wrote: > Our current sprint started Thursday June 26 and ends Tuesday July 8th. > [...] > http://sb.wmflabs.org/t/analytics-developers/2014-06-26/ Thanks Kevin! But as the items on that page might (and already did) change during the sprin

[Analytics] Team's Sprint Commitments

2014-07-01 Thread Kevin Leduc
Greetings, The analytics engineering team is now using ScrumBugs to manage and track it's commitments for every Sprint (2 week iterations). Our current sprint started Thursday June 26 and ends Tuesday July 8th. You can see the Stories (features) and bugs we are presently working on: http://sb.wm