Hello all!
I’m writing to solicit feedback on a plan to slightly rework the Discovery workboards on Phabricator.
Back when we were assembling the team and putting the process together, I expressed a strong desire to have a centralised Discovery workboard which would contain every task related to Discovery’s work. In the end, I’d say that hasn’t really worked out, because there’s simply too many tasks in the workboard and too much in flight. It’s been hard to sensibly break things down into different categories of task on a per-project basis. To help alleviate this problem, here’s my proposal:
- The Discovery workboard is disabled. - The Discovery tag will continue to exist as a parent-tag for Discovery’s work, but there will be no associated workboard. - Individual backlog workboards can be created for individual projects at the request of that team, for example: - Discovery-Search-Backlog - Discovery-Analysis-Backlog - Sprint boards will remain exactly as they are presently.
How will this affect you? Firstly, this won’t affect you at all unless you spend a significant amount of time in the Discovery backlog, which should mostly be! Otherwise, nothing will really change for you. The workflow of engineers working on Maps and Wikidata Query Service, for example, will likely be completely unaffected by this change.
As I’m the primary consumer of the Discovery board, and it’s not working very well for me at the minute, I’d like to move forwards with this proposal unless there are any strong objections. Kevin and I will handle all the logistics.
Thoughts?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
How do we imagine this process could feeding back into product page on meta?
--tomasz
On Fri, Mar 4, 2016 at 2:37 PM, Dan Garry dgarry@wikimedia.org wrote:
Hello all!
I’m writing to solicit feedback on a plan to slightly rework the Discovery workboards on Phabricator.
Back when we were assembling the team and putting the process together, I expressed a strong desire to have a centralised Discovery workboard which would contain every task related to Discovery’s work. In the end, I’d say that hasn’t really worked out, because there’s simply too many tasks in the workboard and too much in flight. It’s been hard to sensibly break things down into different categories of task on a per-project basis. To help alleviate this problem, here’s my proposal:
The Discovery workboard is disabled.
The Discovery tag will continue to exist as a parent-tag for Discovery’s work, but there will be no associated workboard.
Individual backlog workboards can be created for individual projects at the request of that team, for example:
Discovery-Search-Backlog Discovery-Analysis-Backlog
Sprint boards will remain exactly as they are presently.
How will this affect you? Firstly, this won’t affect you at all unless you spend a significant amount of time in the Discovery backlog, which should mostly be! Otherwise, nothing will really change for you. The workflow of engineers working on Maps and Wikidata Query Service, for example, will likely be completely unaffected by this change.
As I’m the primary consumer of the Discovery board, and it’s not working very well for me at the minute, I’d like to move forwards with this proposal unless there are any strong objections. Kevin and I will handle all the logistics.
Thoughts?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
On 7 March 2016 at 15:22, Tomasz Finc tfinc@wikimedia.org wrote:
How do we imagine this process could feeding back into product page on meta?
I'm not sure what you mean. Could you explain?
Thanks, Dan
s/meta/mediawiki
https://www.mediawiki.org/wiki/Wikimedia_Product
I want to make sure we have an easy way to keep that page up to date even if we split up the boards.
--tomasz
On Mon, Mar 7, 2016 at 4:51 PM, Dan Garry dgarry@wikimedia.org wrote:
On 7 March 2016 at 15:22, Tomasz Finc tfinc@wikimedia.org wrote:
How do we imagine this process could feeding back into product page on meta?
I'm not sure what you mean. Could you explain?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
On 7 March 2016 at 17:01, Tomasz Finc tfinc@wikimedia.org wrote:
https://www.mediawiki.org/wiki/Wikimedia_Product
I want to make sure we have an easy way to keep that page up to date even if we split up the boards.
Aha! Thanks for clarifying.
As it stands, we're the odd one out for having a single department-wide workboard. I don't expect that this will affect those updates much, because our updates are not done from scouring the Phabricator Discovery board, but from looking at individual sprints and emails and picking the nicest stuff.
Thanks, Dan
Hmm. Here's this thing that mostly only affects Dan which can be changed to make Dan's life better, and any changes will be almost unnoticed by everyone else. Dan's roped Kevin in to helping him do all the work, and the rest of us don't have to do anything. I dunno. Sounds sketchy.
Of course you should do it!
Trey Jones Software Engineer, Discovery Wikimedia Foundation
On Fri, Mar 4, 2016 at 5:37 PM, Dan Garry dgarry@wikimedia.org wrote:
Hello all!
I’m writing to solicit feedback on a plan to slightly rework the Discovery workboards on Phabricator.
Back when we were assembling the team and putting the process together, I expressed a strong desire to have a centralised Discovery workboard which would contain every task related to Discovery’s work. In the end, I’d say that hasn’t really worked out, because there’s simply too many tasks in the workboard and too much in flight. It’s been hard to sensibly break things down into different categories of task on a per-project basis. To help alleviate this problem, here’s my proposal:
- The Discovery workboard is disabled.
- The Discovery tag will continue to exist as a parent-tag for Discovery’s work, but there will be no associated workboard.
- Individual backlog workboards can be created for individual projects
at the request of that team, for example:
- Discovery-Search-Backlog
- Discovery-Analysis-Backlog
- Sprint boards will remain exactly as they are presently.
How will this affect you? Firstly, this won’t affect you at all unless you spend a significant amount of time in the Discovery backlog, which should mostly be! Otherwise, nothing will really change for you. The workflow of engineers working on Maps and Wikidata Query Service, for example, will likely be completely unaffected by this change.
As I’m the primary consumer of the Discovery board, and it’s not working very well for me at the minute, I’d like to move forwards with this proposal unless there are any strong objections. Kevin and I will handle all the logistics.
Thoughts?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
Hi,
I rarely use this dashboard and I agree with you: when I look at it I can't imagine how hard it can be for you :) I have absolutely no objection.
Le 04/03/2016 23:37, Dan Garry a écrit :
Hello all!
I’m writing to solicit feedback on a plan to slightly rework the Discovery workboards on Phabricator.
Back when we were assembling the team and putting the process together, I expressed a strong desire to have a centralised Discovery workboard which would contain every task related to Discovery’s work. In the end, I’d say that hasn’t really worked out, because there’s simply too many tasks in the workboard and too much in flight. It’s been hard to sensibly break things down into different categories of task on a per-project basis. To help alleviate this problem, here’s my proposal:
- The Discovery workboard is disabled. o The Discovery tag will continue to exist as a parent-tag for Discovery’s work, but there will be no associated workboard.
- Individual backlog workboards can be created for individual projects at the request of that team, for example: o Discovery-Search-Backlog o Discovery-Analysis-Backlog
- Sprint boards will remain exactly as they are presently.
How will this affect you? Firstly, this won’t affect you at all unless you spend a significant amount of time in the Discovery backlog, which should mostly be! Otherwise, nothing will really change for you. The workflow of engineers working on Maps and Wikidata Query Service, for example, will likely be completely unaffected by this change.
As I’m the primary consumer of the Discovery board, and it’s not working very well for me at the minute, I’d like to move forwards with this proposal unless there are any strong objections. Kevin and I will handle all the logistics.
Thoughts?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
Let's do it :)
On Tue, Mar 8, 2016 at 7:11 AM, David Causse dcausse@wikimedia.org wrote:
Hi,
I rarely use this dashboard and I agree with you: when I look at it I can't imagine how hard it can be for you :) I have absolutely no objection.
Le 04/03/2016 23:37, Dan Garry a écrit :
Hello all!
I’m writing to solicit feedback on a plan to slightly rework the Discovery workboards on Phabricator.
Back when we were assembling the team and putting the process together, I expressed a strong desire to have a centralised Discovery workboard which would contain every task related to Discovery’s work. In the end, I’d say that hasn’t really worked out, because there’s simply too many tasks in the workboard and too much in flight. It’s been hard to sensibly break things down into different categories of task on a per-project basis. To help alleviate this problem, here’s my proposal:
The Discovery workboard is disabled.
The Discovery tag will continue to exist as a parent-tag for Discovery’s work, but there will be no associated workboard.
Individual backlog workboards can be created for individual projects at the request of that team, for example:
Discovery-Search-Backlog Discovery-Analysis-Backlog
Sprint boards will remain exactly as they are presently.
How will this affect you? Firstly, this won’t affect you at all unless you spend a significant amount of time in the Discovery backlog, which should mostly be! Otherwise, nothing will really change for you. The workflow of engineers working on Maps and Wikidata Query Service, for example, will likely be completely unaffected by this change.
As I’m the primary consumer of the Discovery board, and it’s not working very well for me at the minute, I’d like to move forwards with this proposal unless there are any strong objections. Kevin and I will handle all the logistics.
Thoughts?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
Thanks all. Kevin and I will work on the migration, and keep this list posted.
Dan
On 8 March 2016 at 10:21, Tomasz Finc tfinc@wikimedia.org wrote:
Let's do it :)
On Tue, Mar 8, 2016 at 7:11 AM, David Causse dcausse@wikimedia.org wrote:
Hi,
I rarely use this dashboard and I agree with you: when I look at it I
can't
imagine how hard it can be for you :) I have absolutely no objection.
Le 04/03/2016 23:37, Dan Garry a écrit :
Hello all!
I’m writing to solicit feedback on a plan to slightly rework the
Discovery
workboards on Phabricator.
Back when we were assembling the team and putting the process together, I expressed a strong desire to have a centralised Discovery workboard which would contain every task related to Discovery’s work. In the end, I’d say that hasn’t really worked out, because there’s simply too many tasks in
the
workboard and too much in flight. It’s been hard to sensibly break things down into different categories of task on a per-project basis. To help alleviate this problem, here’s my proposal:
The Discovery workboard is disabled.
The Discovery tag will continue to exist as a parent-tag for Discovery’s work, but there will be no associated workboard.
Individual backlog workboards can be created for individual projects at
the
request of that team, for example:
Discovery-Search-Backlog Discovery-Analysis-Backlog
Sprint boards will remain exactly as they are presently.
How will this affect you? Firstly, this won’t affect you at all unless
you
spend a significant amount of time in the Discovery backlog, which should mostly be! Otherwise, nothing will really change for you. The workflow of engineers working on Maps and Wikidata Query Service, for example, will likely be completely unaffected by this change.
As I’m the primary consumer of the Discovery board, and it’s not working very well for me at the minute, I’d like to move forwards with this
proposal
unless there are any strong objections. Kevin and I will handle all the logistics.
Thoughts?
Thanks, Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery