This email is aimed at members of the Search team, so anyone else can freely ignore it. It was easier for me to send it to this list, and it seemed like it could be beneficial to have others aware of the issues that came up.
Here is a list of all the ideas that came up during the recent search retrospective. I encourage further discussion about them, either in this thread, or in a new thread per item/cluster, or in the talk page for the retro itself[1], or elsewhere.
- Do people want more feedback on their work/way [We discussed this, and Erika has an action item to follow up] - In hangouts, make sure you are on screen when speaking [Note that although you see yourself in a rectangle, everyone else only sees you as a square] - do we need a fully documented checklist on how to update the portal? - automate our maven deployment / release process - Find a way to fluently enable new search keywords that need reindex/new data - Running A/B tests is a very slow feedback loop - Getting feedback on things that are still internal, before releasing to the world - Weekly sprint planning meeting has a variable agenda - Does Cross-Wiki work still need its own column on the Search workboard? - We sometime focus too much on having efficient meetings [Kevin has an action item for this] - Product (user?) Testing: I'd like to see if there's ways we could expand our testing "toolbelt" - Do we need to foster more knowledge sharing between areas of expertise? [Erika has an action item for this] - How to bring in outside people/organizations that want to help (converting interest into a contract or other formal agreement) - This quarter has been a little lighter on community discussion
[1] https://www.mediawiki.org/wiki/Wikimedia_Discovery/Meetings/Search_retrospec...
Kevin Smith Agile Coach, Wikimedia Foundation
On Tue, Mar 7, 2017 at 7:11 PM, Kevin Smith ksmith@wikimedia.org wrote:
This email is aimed at members of the Search team, so anyone else can freely ignore it. It was easier for me to send it to this list, and it seemed like it could be beneficial to have others aware of the issues that came up.
Here is a list of all the ideas that came up during the recent search retrospective. I encourage further discussion about them, either in this thread, or in a new thread per item/cluster, or in the talk page for the retro itself[1], or elsewhere.
Do people want more feedback on their work/way [We discussed this, and Erika has an action item to follow up] In hangouts, make sure you are on screen when speaking [Note that although you see yourself in a rectangle, everyone else only sees you as a square] do we need a fully documented checklist on how to update the portal?
Full documented checklist might be too much, but I can't even find a page on wikitech about portals (this probably tells more about my ability to navigate wikitech than about the fact that this page exists). There is some documentation inside the project itself [1][2], but more oriented toward contributing / development than about deployment.
automate our maven deployment / release process
Some improvements to elasticsearch plugins already [3]. I'll probably follow up with Stas to see if we can do something on WDQS as well.
Find a way to fluently enable new search keywords that need reindex/new data Running A/B tests is a very slow feedback loop Getting feedback on things that are still internal, before releasing to the world Weekly sprint planning meeting has a variable agenda Does Cross-Wiki work still need its own column on the Search workboard? We sometime focus too much on having efficient meetings [Kevin has an action item for this] Product (user?) Testing: I'd like to see if there's ways we could expand our testing "toolbelt" Do we need to foster more knowledge sharing between areas of expertise? [Erika has an action item for this] How to bring in outside people/organizations that want to help (converting interest into a contract or other formal agreement) This quarter has been a little lighter on community discussion
[1] https://www.mediawiki.org/wiki/Wikimedia_Discovery/Meetings/Search_retrospec...
[1] https://github.com/wikimedia/portals/blob/master/README.md [2] https://github.com/wikimedia/portals/blob/master/CONTRIBUTING.md [3] https://gerrit.wikimedia.org/r/#/c/340947/
Kevin Smith Agile Coach, Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
On 7 March 2017 at 18:11, Kevin Smith ksmith@wikimedia.org wrote:
- Weekly sprint planning meeting has a variable agenda
This is very useful feedback for me!
The retrospective notes page says these agenda items are typically included:
1. check on how quarterly goals are proceeding 2. check whether everyone has enough work 3. triage the workboard
It was noted that each of these are useful, but that which of them we do in any given meeting can vary.
I will Be Bold™ and propose that we try doing three all of these starting in today's sprint planning meeting. If we feel this doesn't work for whatever reason, we can discuss and adjust.
- We sometime focus too much on having efficient meetings [Kevin has
an action item for this]
I assume this was in part a reference to the weekly meeting; does it also
apply to the sprint planning meeting? If so, what kind of other things do we think might be useful to include?
Thanks!
Dan
On 14 March 2017 at 15:45, Dan Garry dgarry@wikimedia.org wrote:
I will Be Bold™ and propose that we try doing three all of these starting in today's sprint planning meeting. If we feel this doesn't work for whatever reason, we can discuss and adjust.
Meeting description updated.
I also continued Being Bold™ and added a fourth item for open discussions of relevant matters, such as proposed new quarterly goals. We've done this a few times and it seems to have been useful, so adding it as an agenda item seemed to make sense.
Thanks, Dan