A question of handling of stalled storiescame up during the Sprint 18
retrospective. Examples of such stories include ones that are never
being picked up and stay "new" and stories that reach "ready for
testing" stateand stall in that state.
One of the approaches I can think of to help with the former issueis to
go over the backlog in the middle of the sprint and see which stories
have not been picked up (and possibly assign them to developers). This
can be done during the scrum callor during the mid-sprint deep dive/demo.
Based on the conversation about stories stalled in "ready for testing"
state, it would appear that the main culprit is lack of PR
reviews/feedback. I think a good venue to resolve this issue/solicit
help is scrum-- The author of the PR should mention that they are being
blocked by lack of reviews/feedback.
Thoughts/opinions?
-d
I'll start using that tactic from today on.
It'd be nice if we could have a ranking of stalled PR sorted by days with
no comment so that we can identify this stuff, I vaguely recall seeing
something like that in the past but I don't remember the name of the tool…
···
On Mon, Jan 13, 2014 at 1:36 PM, Dmitri Dolguikh wrote:
A question of handling of stalled storiescame up during the Sprint 18
retrospective. Examples of such stories include ones that are never
being picked up and stay “new” and stories that reach “ready for
testing” stateand stall in that state.
One of the approaches I can think of to help with the former issueis to
go over the backlog in the middle of the sprint and see which stories
have not been picked up (and possibly assign them to developers). This
can be done during the scrum callor during the mid-sprint deep dive/demo.
Based on the conversation about stories stalled in "ready for testing"
state, it would appear that the main culprit is lack of PR
reviews/feedback. I think a good venue to resolve this issue/solicit
help is scrum-- The author of the PR should mention that they are being
blocked by lack of reviews/feedback.
Thoughts/opinions?
-d
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Daniel Lobato
@elobatoss
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> I'll start using that tactic from today on.
>
> It'd be nice if we could have a ranking of stalled PR sorted by days with no
> comment so that we can identify this stuff, I vaguely recall seeing
> something like that in the past but I don't remember the name of the tool…
Dominic – we could probably split the ranking bit between the two of
us? A few minutes a day should be sufficient to keep the sprint
backlog sorted based on story priorities…
-d
···
On Tue, Jan 14, 2014 at 12:15 PM, Daniel Lobato wrote:
On Mon, Jan 13, 2014 at 1:36 PM, Dmitri Dolguikh witlessbird@gmail.com > wrote:
A question of handling of stalled storiescame up during the Sprint 18
retrospective. Examples of such stories include ones that are never
being picked up and stay “new” and stories that reach “ready for
testing” stateand stall in that state.
One of the approaches I can think of to help with the former issueis to
go over the backlog in the middle of the sprint and see which stories
have not been picked up (and possibly assign them to developers). This
can be done during the scrum callor during the mid-sprint deep dive/demo.
Based on the conversation about stories stalled in "ready for testing"
state, it would appear that the main culprit is lack of PR
reviews/feedback. I think a good venue to resolve this issue/solicit
help is scrum-- The author of the PR should mention that they are being
blocked by lack of reviews/feedback.
Thoughts/opinions?
-d
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Daniel Lobato
@elobatoss
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
You might thinking of http://gitofdespair.herokuapp.com/theforeman,
which Ohad likes.
I also use the sorting on the GitHub PR list, which can be helpful.
···
On 14/01/14 12:15, Daniel Lobato wrote:
> I'll start using that tactic from today on.
>
> It'd be nice if we could have a ranking of stalled PR sorted by days
> with no comment so that we can identify this stuff, I vaguely recall
> seeing something like that in the past but I don't remember the name of
> the tool..
–
Dominic Cleal
Red Hat Engineering
Sure, that would be good.
···
On 14/01/14 12:18, Dmitri Dolguikh wrote:
> On Tue, Jan 14, 2014 at 12:15 PM, Daniel Lobato wrote:
>> I'll start using that tactic from today on.
>>
>> It'd be nice if we could have a ranking of stalled PR sorted by days with no
>> comment so that we can identify this stuff, I vaguely recall seeing
>> something like that in the past but I don't remember the name of the tool..
>
> Dominic -- we could probably split the ranking bit between the two of
> us? A few minutes a day should be sufficient to keep the sprint
> backlog sorted based on story priorities�
> -d
–
Dominic Cleal
Red Hat Engineering
