Story #2265
closed
As developers we can plan our sprints in an IRC meeting
0%
Description
IRC meetings offer many benefits
- Using our own machines
- Separate cognitive tasks of reading, listening, and speaking
- Pulpbot assistance
- Outside participants
- publicly available logs
An important difference from triage is that Sprint Planning is not about each issue in isolation, we need to be able to weigh the priority of one issue vs another. The order that issues are discussed matters to the efficiency of the meeting, because we want to make sure that the most important work is put on the sprint first so we don't have to take less important work off to make room later.
Another item to consider is whether we want to use an IRC bot and how we want to use it.
For an initial pass at a possible implementation see this etherpad:
http://pulp.etherpad.corp.redhat.com/274
Updated by semyers over 6 years ago
The triage bot can sorta do this, but at the moment is too coupled with the idea of triaging to be easily modified to this task. I do think the work could be done inside a sprint, though.
I'm already in the process of "genericizing" issue iteration and the issue proposal system, but it's a side project that I mess with only occasionaly and progress is slow.
That all said, if we can decouple bits of the triage workflow from triage itself (like the proposal system, the redmine report iterator), making them reusable for other workflows (like sprint planning), I think it could be a good solution to this, and possibly make way for other IRC-based workflows that we might want.
Updated by amacdona@redhat.com over 6 years ago
- Sprint Candidate changed from No to Yes
Updated by amacdona@redhat.com over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
.