Hi,
As your inbox might have noticed, I spent some time triaging the Echo board https://phabricator.wikimedia.org/tag/echo/. I didn't really change priorities, mainly focused on the columns.
The board now has 5 columns: * Backlog - default, untriaged. Should be empty most of the time, it isn't right now because I didn't finish. * Needs plan - still under discussion, doesn't have a clear direction or obvious reproduction steps. * Needs code - Ready for someone to pick up and write code! May not always be code related though (ex: "some images need to be reversed for RTL languages"). * In progress - in progress, should always have an assignee. * External - Things related to Echo we should be aware of, but not necessarily something we need to work on.
This is based off of the board we've been using for the MediaWiki-API[1] project, which I've found generally works well. If I mis-triaged stuff, please re-triage as necessary :)
[1] https://phabricator.wikimedia.org/tag/mediawiki-api/
-- Kunal
On 07/06/2015 06:19 AM, Kunal Mehta wrote:
Hi,
As your inbox might have noticed, I spent some time triaging the Echo board https://phabricator.wikimedia.org/tag/echo/. I didn't really change priorities, mainly focused on the columns.
How is this meant to interact with our main backlog board (https://phabricator.wikimedia.org/tag/echo/)? Some of the columns seem to have the same purpose ("Needs plan" on Echo vs. "Design / Requirements" on Collaboration-Team.
Matt
On Mon, Jul 6, 2015 at 2:03 PM, Matthew Flaschen mflaschen@wikimedia.org wrote:
How is this meant to interact with our main backlog board (https://phabricator.wikimedia.org/tag/echo/)? Some of the columns seem to have the same purpose ("Needs plan" on Echo vs. "Design / Requirements" on Collaboration-Team.
Did you mean https://phabricator.wikimedia.org/project/sprint/board/65/ ?
I have the same concern: we need to decide whether we want to have a team-wide board or a project wide board, or have both with clearly different purposes. Right now there appears to be overlap.
Roan
The "Collaboration-Team Workboard" should be the backlog for all of our projects. I think project-specific boards will probably be the graveyard where ignored tickets go to die. :)
We're building sprints from that workboard, so all the tickets should be there.
Also, Kunal -- thank you for triaging stuff! :)
On Mon, Jul 6, 2015 at 2:11 PM, Roan Kattouw rkattouw@wikimedia.org wrote:
On Mon, Jul 6, 2015 at 2:03 PM, Matthew Flaschen mflaschen@wikimedia.org wrote:
How is this meant to interact with our main backlog board (
https://phabricator.wikimedia.org/tag/echo/)? Some of the columns seem to have the same purpose ("Needs plan" on Echo vs. "Design / Requirements" on Collaboration-Team.
Did you mean https://phabricator.wikimedia.org/project/sprint/board/65/ ?
I have the same concern: we need to decide whether we want to have a team-wide board or a project wide board, or have both with clearly different purposes. Right now there appears to be overlap.
Roan
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
On 07/06/2015 05:11 PM, Roan Kattouw wrote:
On Mon, Jul 6, 2015 at 2:03 PM, Matthew Flaschen mflaschen@wikimedia.org wrote:
How is this meant to interact with our main backlog board (https://phabricator.wikimedia.org/tag/echo/)? Some of the columns seem to have the same purpose ("Needs plan" on Echo vs. "Design / Requirements" on Collaboration-Team.
Did you mean https://phabricator.wikimedia.org/project/sprint/board/65/ ?
I have the same concern: we need to decide whether we want to have a team-wide board or a project wide board, or have both with clearly different purposes. Right now there appears to be overlap.
Yes, I meant Collaboration-Team/65. I agree with Danny we should have a single backlog board. If people are in agreement, let's port the relevant triaging over to Collaboration-Team, then delete the Echo-specific columns.
Also, anything that we work on during the sprint (even if not originally in the sprint) can be added to the sprint board (with obvious caveats about not ignoring the original sprint commitment).
Matt