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_retrospe… Kevin Smith Agile Coach, Wikimedia Foundation