Comments for Gojko Adzic http://gojko.net Building software that matters Tue, 21 Feb 2012 12:52:01 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Splitting user stories: the hamburger method by Andrej Telle http://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/comment-page-1/#comment-209509 Andrej Telle Tue, 21 Feb 2012 12:52:01 +0000 http://gojko.net/?p=2699#comment-209509 I really like the approach of splitting one user story into many different and then deciding on what implementation to develop considering effort and complexity vs. business value. However, wouldn't it be smarter to simply split all of them into single user stories and group them as a feature. My point being that in a lean and agile environment you wouldn't have to wait for every single of the steps being implemented in any shape or form, you could just go and deploy step by step. And reaccess the results as you go along... You actually suggest something similar by leaving out certain steps, however the user story as a whole does not get finished... Which might be a motivational drawback to the team, don't you think? I really like the approach of splitting one user story into many different and then deciding on what implementation to develop considering effort and complexity vs. business value.

However, wouldn’t it be smarter to simply split all of them into single user stories and group them as a feature. My point being that in a lean and agile environment you wouldn’t have to wait for every single of the steps being implemented in any shape or form, you could just go and deploy step by step. And reaccess the results as you go along…

You actually suggest something similar by leaving out certain steps, however the user story as a whole does not get finished… Which might be a motivational drawback to the team, don’t you think?

]]> Comment on Visualising quality: initial ideas by Kerry Kimbrough http://gojko.net/2011/04/27/visualising-quality-initial-ideas/comment-page-1/#comment-207646 Kerry Kimbrough Tue, 14 Feb 2012 22:16:16 +0000 http://gojko.net/?p=2379#comment-207646 Good discussion on an important topic! Although you are still confused about what you are visualizing. Is it quality? No, you show only predictions of quality. From strictly technical indicators, no less! Quality is value to some person and we, as the producers, are not that person! Your bridge building analogy is pointless. Of course, we will do our professional best to deliver high quality results -- no one is proposing carelessness. All these defect statistics! At best, they indicate the execution of our intentions. But surely the assumption that our intentions match customers' real values is our greatest risk, with the most direct impact on delivered quality. Why aren't you visualizing that? Your effect maps are powerful visualizations of the link between stories and value. Why not superimpose on them the "heat" of open defects? Or the "heat" of incomplete testing? Good discussion on an important topic! Although you are still confused about what you are visualizing. Is it quality? No, you show only predictions of quality. From strictly technical indicators, no less! Quality is value to some person and we, as the producers, are not that person! Your bridge building analogy is pointless. Of course, we will do our professional best to deliver high quality results — no one is proposing carelessness. All these defect statistics! At best, they indicate the execution of our intentions. But surely the assumption that our intentions match customers’ real values is our greatest risk, with the most direct impact on delivered quality. Why aren’t you visualizing that? Your effect maps are powerful visualizations of the link between stories and value. Why not superimpose on them the “heat” of open defects? Or the “heat” of incomplete testing?

]]> Comment on Splitting user stories: the hamburger method by Dan Bergh Johnsson http://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/comment-page-1/#comment-203492 Dan Bergh Johnsson Thu, 02 Feb 2012 07:12:46 +0000 http://gojko.net/?p=2699#comment-203492 Really nice metaphor. I have been talking about "slicing the cheese/cake in another direction", and I have also been talking about sandwich-eating. Howver, "hamburger" strikes a much stronger association. Nice one. Really nice metaphor. I have been talking about “slicing the cheese/cake in another direction”, and I have also been talking about sandwich-eating. Howver, “hamburger” strikes a much stronger association. Nice one.

]]> Comment on Splitting user stories: the hamburger method by Gishu http://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/comment-page-1/#comment-202900 Gishu Tue, 31 Jan 2012 14:24:44 +0000 http://gojko.net/?p=2699#comment-202900 So when is the hamburger really "done" - what's the done definition for this story ? Does the user make an entry at any point until the entire hamburger is done? Do you demo interim bites and let the customer decide on acceptable quality ? So when is the hamburger really “done” – what’s the done definition for this story ? Does the user make an entry at any point until the entire hamburger is done? Do you demo interim bites and let the customer decide on acceptable quality ?

]]> Comment on Splitting user stories: the hamburger method by Portia Tung http://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/comment-page-1/#comment-202890 Portia Tung Tue, 31 Jan 2012 13:31:34 +0000 http://gojko.net/?p=2699#comment-202890 What a fun way of thinking about story/task decomposition, re-composition and Real Options Thinking! The User Story Hamburger Method describes what I've done with teams in the past to great effect - only this metaphor is a lot more fun and more appetising! Good job, Gojko. Thanks! What a fun way of thinking about story/task decomposition, re-composition and Real Options Thinking!

The User Story Hamburger Method describes what I’ve done with teams in the past to great effect – only this metaphor is a lot more fun and more appetising!

Good job, Gojko. Thanks!

]]>