Comments on: Flow to READY, Iterate to DONE http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/ Thu, 18 Mar 2010 13:27:36 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: the random noise generator » Blog Archive » A personal look back on XP Days Benelux 2009 http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-93260 the random noise generator » Blog Archive » A personal look back on XP Days Benelux 2009 Sun, 29 Nov 2009 16:32:02 +0000 http://blog.xebia.com/?p=2407#comment-93260 [...] approach to agile coaching. Another BoF was run by Serge Beaumont on practical tools, like the Ready state and Jeff Patton’s Story Mapping for the Product Owner. Both BoFs have noticeably created a [...] [...] approach to agile coaching. Another BoF was run by Serge Beaumont on practical tools, like the Ready state and Jeff Patton’s Story Mapping for the Product Owner. Both BoFs have noticeably created a [...]

]]> By: Rafael Lima » Papéis no SCRUM - Você sabe responder? http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92304 Rafael Lima » Papéis no SCRUM - Você sabe responder? Tue, 18 Aug 2009 18:16:50 +0000 http://blog.xebia.com/?p=2407#comment-92304 [...] Atualização em 18/08/09 - Depois de esvaziar o buffer neste post, continuei lendo e pesquisando sorbe o assunto. Pretendo formatar um modelo que funcione bem para as características específicas aqui da Myfreecomm. Nas leituras achei este post que responde exatamente as minhas perguntas. [...] [...] Atualização em 18/08/09 – Depois de esvaziar o buffer neste post, continuei lendo e pesquisando sorbe o assunto. Pretendo formatar um modelo que funcione bem para as características específicas aqui da Myfreecomm. Nas leituras achei este post que responde exatamente as minhas perguntas. [...]

]]> By: ADSystems – Agile Development Blog » Particione seu Backlog para Quilometragem Máxima http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92258 ADSystems – Agile Development Blog » Particione seu Backlog para Quilometragem Máxima Fri, 07 Aug 2009 22:00:36 +0000 http://blog.xebia.com/?p=2407#comment-92258 [...] disso, para dar mais sentido para o backlog, Serge Beaumont sugeriu um interessante modo de particionar o backlog o qual mapeia para um fluxo e faz com que o backlog tenha sua existência [...] [...] disso, para dar mais sentido para o backlog, Serge Beaumont sugeriu um interessante modo de particionar o backlog o qual mapeia para um fluxo e faz com que o backlog tenha sua existência [...]

]]> By: Serge Beaumont http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92254 Serge Beaumont Thu, 06 Aug 2009 15:50:05 +0000 http://blog.xebia.com/?p=2407#comment-92254 @Yuval: The flow style I suggest is independent of the granularity of the backlog items: I consider this to be an orthogonal issue. I tend to add one (or more, depending on how much you're scaling) layer on top of the fine-grained backlog (which is nice for the team) that is coarser grained (which is nice for the PO's overview: seeing the trees for the forest). I have done some large scale implementations with multiple (8) teams, where I introduced a higher level backlog that represents the strategic goals of the company: all lower level backlogs would point up at the strategic one. Another trick is to have an "epic type" that is not part of the backlog proper, but only there to connect related user stories. There's many ways to do this, but in the end I'd say that what you're "atomically flowing" is your finest-grained level, whatever it may be. As to sprinting the same backlog, that's perfectly fine. The only situation you want to avoid is one team sprinting multiple backlogs because that pushes PO work (integrating the two backlogs) into the team. @Yuval: The flow style I suggest is independent of the granularity of the backlog items: I consider this to be an orthogonal issue. I tend to add one (or more, depending on how much you’re scaling) layer on top of the fine-grained backlog (which is nice for the team) that is coarser grained (which is nice for the PO’s overview: seeing the trees for the forest). I have done some large scale implementations with multiple (8) teams, where I introduced a higher level backlog that represents the strategic goals of the company: all lower level backlogs would point up at the strategic one. Another trick is to have an “epic type” that is not part of the backlog proper, but only there to connect related user stories. There’s many ways to do this, but in the end I’d say that what you’re “atomically flowing” is your finest-grained level, whatever it may be.

As to sprinting the same backlog, that’s perfectly fine. The only situation you want to avoid is one team sprinting multiple backlogs because that pushes PO work (integrating the two backlogs) into the team.

]]> By: Bugs Source #1: Unclear User Stories | Edge of Chaos | Agile Development Blog http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92253 Bugs Source #1: Unclear User Stories | Edge of Chaos | Agile Development Blog Thu, 06 Aug 2009 10:31:25 +0000 http://blog.xebia.com/?p=2407#comment-92253 [...] to document more user stories than required, and it will be a form of a waste. Product Owner should maintain good balance here. var dzone_style="2";SHARETHIS.addEntry({ title: "Bugs Source #1: Unclear User Stories", url: [...] [...] to document more user stories than required, and it will be a form of a waste. Product Owner should maintain good balance here. var dzone_style=”2″;SHARETHIS.addEntry({ title: “Bugs Source #1: Unclear User Stories”, url: [...]

]]> By: Carsten Ruseng Jakobsen http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92242 Carsten Ruseng Jakobsen Tue, 04 Aug 2009 09:14:49 +0000 http://blog.xebia.com/?p=2407#comment-92242 I really find this blog well-written and good! I agree with Serges point above in separating the work of PO from the work of the Team. Otherwise it is very difficult to establish a stable continous flow for the Team. Also the nature of the PO's work is often more disruptive. I really find this blog well-written and good!
I agree with Serges point above in separating the work of PO from the work of the Team. Otherwise it is very difficult to establish a stable continous flow for the Team. Also the nature of the PO’s work is often more disruptive.

]]> By: Yuval Yeret http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92224 Yuval Yeret Sun, 02 Aug 2009 15:10:09 +0000 http://blog.xebia.com/?p=2407#comment-92224 I like this very much. In one of the companies I'm consulting to we are trying to indeed create a flowing process for backlog creation, and this is very inline with what we have in mind. A key question though is how to deal with scale, namely if you are working on big projects with many teams, you need to decide at what level you are tracking on this kanban. Is it Features/Epics/Stories? One thing I'm thinking of is maybe tracking at the level that originally goes into the backlog, but if during the "preparing" stage you understand its comprised of more stories you can move the tracking to this level (and throw away the original story? leave it as an aggregate?) This sounds like an area where Minimally-Marketable-Features (MMF) can come into play nicely - maybe you want to track at the MMF level, and if you understand something can be effectively split to two or more MMFs, fine! Another scaling issue is if you have multiple teams that are sprinting the same backlog, or even multiple component teams sprinting the same project (and having each their internal component backlog) - I know its not a recommended structure but one that happens in really large scale until the Feature-team approach really takes flight... ;-) Any thoughts? I like this very much. In one of the companies I’m consulting to we are trying to indeed create a flowing process for backlog creation, and this is very inline with what we have in mind.

A key question though is how to deal with scale, namely if you are working on big projects with many teams, you need to decide at what level you are tracking on this kanban. Is it Features/Epics/Stories?
One thing I’m thinking of is maybe tracking at the level that originally goes into the backlog, but if during the “preparing” stage you understand its comprised of more stories you can move the tracking to this level (and throw away the original story? leave it as an aggregate?)

This sounds like an area where Minimally-Marketable-Features (MMF) can come into play nicely – maybe you want to track at the MMF level, and if you understand something can be effectively split to two or more MMFs, fine!

Another scaling issue is if you have multiple teams that are sprinting the same backlog, or even multiple component teams sprinting the same project (and having each their internal component backlog) – I know its not a recommended structure but one that happens in really large scale until the Feature-team approach really takes flight… ;-)

Any thoughts?

]]> By: Twitted by jhollingworth http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92150 Twitted by jhollingworth Thu, 23 Jul 2009 08:29:40 +0000 http://blog.xebia.com/?p=2407#comment-92150 [...] This post was Twitted by jhollingworth [...] [...] This post was Twitted by jhollingworth [...]

]]> By: Scrum READY state ? « Pragmatic Agile Weblog http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92084 Scrum READY state ? « Pragmatic Agile Weblog Tue, 14 Jul 2009 23:16:17 +0000 http://blog.xebia.com/?p=2407#comment-92084 [...] http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/ [...] [...] http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/ [...]

]]> By: Fabrice Aimetti http://blog.xebia.com/2009/07/04/flow-to-ready-iterate-to-done/comment-page-1/#comment-92077 Fabrice Aimetti Mon, 13 Jul 2009 22:47:44 +0000 http://blog.xebia.com/?p=2407#comment-92077 Hello Serge, Thanks for this excellent article. You fill find its french translation on <a href="http://www.fabrice-aimetti.fr/dotclear/index.php?post/2009/07/13/Preparer-le-PRET-Iterer-jusqu-a-TERMINE" rel="nofollow">Préparer le PRÊT - Itérer jusqu'à TERMINÉ</a>. Regards. Hello Serge, Thanks for this excellent article. You fill find its french translation on Préparer le PRÊT – Itérer jusqu’à TERMINÉ. Regards.

]]>