[16:27:01] ahoy mateys! it'll be "talk like a pirate day" today, ARRRRRR [16:39:51] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: Follow up after 2016-09-13 CR retreat - https://phabricator.wikimedia.org/T145576#2648997 (10ggellerman) We are meeting Tuesday 2016-09-20 [16:52:31] 06Team-Practices, 10TPG-Essential-Functions: Add reevaluation steps to CSAT procedure - https://phabricator.wikimedia.org/T138033#2649057 (10ggellerman) @ksmith and I spoke about suggestion from @aripstra that we could add a question to a future CSAT to ask directly if customers have survey fatigue. We opted... [17:19:52] awjr: jaufrecht: maxbinder: meeple27: kristenlans: I took a spin through the backlog in preparation for today's monthly backlog meeting. I was able to move 6 card to This Week and was able to address one that is already in needs review [17:20:22] ggellerman: far out [17:20:25] cool [17:32:55] Do we have a step in the onboarding checklist to literally turn into a wolf? Or is T&C going to nix that? [17:33:57] ggellerman: 💪 [17:34:21] jaufrecht: i think it's a natural process that occurs once the onboarding checklist is complete [17:44:36] ggellerman: nice pre-wolfing! [17:44:57] thanks! [17:45:06] did you send CSAT on Friday? [18:00:47] kristenlans: running 5 min late [18:01:04] jaufrecht: np [18:02:58] ggellerman: FYI I'm going to ping my LE folks today to try to get a few last responses [18:29:56] jaufrecht: too ^ [18:44:25] Tinker wanted me to add feedback, but the link is broken, and going to Tinkerapp.com shows: [18:44:29] https://www.irccloud.com/pastebin/DoqAv1hP/ [18:44:43] 😦 [18:45:12] I don't know that 😦 adequately conveys my frustration with Tinker. :bom [18:45:52] 💣 🔥 ☁️ 👎 [18:47:43] same here (about tinker) [18:49:31] I really liked Tonkering...when it worked :-) [18:49:45] Tonker? a new fork of Tinker that works? [18:51:17] jaufrecht: Tinker has been down for over a week, but it does helpfully keep sending reminders [19:00:26] that reminds me [19:00:40] i emailed howie about it who said it isn't supposed to be down but acknowledged that it is... [19:01:00] he asked terry (chay not gilbey) to look into it - no word on whether that's happened etc yet [19:22:46] Thanks for pingin Howie awjr [19:32:05] we might have to resort to directly communicating with each other (shudder!) [19:59:50] hi nataliaharateh !!!!!!! [20:02:12] Hello ! It seems like I made it! :D /me waves hello [20:11:54] yeah, you made it! IRC on day one is impressive :-D [20:12:15] I wonder why your /me didn't work [20:12:20] * kristenlans wonders [20:12:29] * nataliaharateh fixes me [20:12:45] I think it's because it was too close to ":D" :) [20:13:18] Ah... [20:15:08] * awjr waves to nataliaharateh [20:15:36] 👋 [20:16:25] o/ [20:22:08] Here's the wolf analogy that didn't show up in the e-mail -> http://i.imgur.com/0dkqCZU.gifv (Me during the first few weeks, please have mercy) [20:23:12] hehehehehe [20:23:50] yes, that looks right. [20:24:11] but we'll help you back up the stairs :) [20:29:43] nataliaharateh: That's probably how it will seem from inside your own head. From outside, we'll probably see at most a tiny slip. With that in mind....1) if you feel like you're falling, let someone know so they can know to help, and 2) try to maintain perspective. [20:30:05] We've all survived the firehose (except awjr who first turned it on) [20:32:13] awjr: you joining? [20:32:24] ack yes [20:32:25] sorry [20:34:59] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: [EPIC] Support CR onsite on 2016-09-13 - https://phabricator.wikimedia.org/T143609#2650165 (10JAufrecht) [20:35:23] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2650170 (10JAufrecht) [20:35:30] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: [EPIC] Administer and process Team Practices Customer Satisfaction survey for FY 2016-17 Q1 (July-Sept 2016) - https://phabricator.wikimedia.org/T142146#2650173 (10JAufrecht) [20:35:38] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: [EPIC] Support CR onsite on 2016-09-13 - https://phabricator.wikimedia.org/T143609#2573337 (10JAufrecht) [20:35:47] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10JAufrecht) [20:36:03] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10JAufrecht) [20:37:45] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2650184 (10ksmith) [20:38:07] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: [EPIC] Determine Phate of Phlogiston - https://phabricator.wikimedia.org/T132365#2650189 (10Awjrichards) [20:38:29] 06Team-Practices, 10TPG-Essential-Functions, 10TPG-FY2016–17-Q1-Identify-Common-Pain: [Epic] Validate statment of purpose of design with all WMF and Wikimedia community - https://phabricator.wikimedia.org/T139998#2650194 (10Awjrichards) [20:44:01] 06Team-Practices, 10TPG-Essential-Functions, 10TPG-FY2016–17-Q1-Identify-Common-Pain: [Epic] Get feedback from design stakeholders at WMF on first draft of 'statement of purpose of design at the WMF' - https://phabricator.wikimedia.org/T139996#2650224 (10Awjrichards) [20:47:11] 06Team-Practices, 10TPG-Essential-Functions: Survey stakeholders for perceived value - https://phabricator.wikimedia.org/T146087#2650255 (10JAufrecht) [20:47:33] 06Team-Practices, 10TPG-Essential-Functions: Create content for Phlogiston value survey - https://phabricator.wikimedia.org/T146088#2650270 (10JAufrecht) [20:49:10] 06Team-Practices, 10TPG-Essential-Functions: Publish the Phlogiston value survey - https://phabricator.wikimedia.org/T146089#2650291 (10JAufrecht) [20:49:15] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey: Refine the Light Engagement survey based on 2nd round results - https://phabricator.wikimedia.org/T141142#2650305 (10ksmith) [20:49:23] 06Team-Practices, 10TPG-Essential-Functions: Survey stakeholders for perceived value - https://phabricator.wikimedia.org/T146087#2650306 (10JAufrecht) [20:49:53] 06Team-Practices, 10TPG-Essential-Functions: Survey stakeholders for perceived value - https://phabricator.wikimedia.org/T146087#2650255 (10JAufrecht) [20:50:39] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: [EPIC] Determine Phate of Phlogiston - https://phabricator.wikimedia.org/T132365#2650336 (10JAufrecht) [21:01:32] I'll skip this one but will join you on Thursday and Friday :) [21:15:38] nataliaharateh: no worries! [21:15:45] 06Team-Practices, 10TPG-Essential-Functions, 07Epic: [EPIC] Administer and process Team Practices Customer Satisfaction survey for FY 2016-17 Q1 (July-Sept 2016) - https://phabricator.wikimedia.org/T142146#2650405 (10ggellerman) [21:16:53] 06Team-Practices, 10TPG-Essential-Functions: Explore how individual TPGers might use CSAT data to improve - https://phabricator.wikimedia.org/T138614#2650407 (10ksmith) 05Open>03declined We decided to update the CSAT documentation to ensure that TPGers have access to the raw data, so can perform whatever a... [21:18:30] 06Team-Practices, 10TPG-Essential-Functions: Add reevaluation steps to CSAT procedure - https://phabricator.wikimedia.org/T138033#2650413 (10Awjrichards) 05Open>03declined We've already baked reevaluating and refining the CSAT into our process, marking declined. [21:22:21] 06Team-Practices, 10TPG-Essential-Functions: Support definition of refined annual planning process - https://phabricator.wikimedia.org/T138246#2650430 (10Awjrichards) 05Open>03declined This task is redundant with T138241 and any ongoing/related activities are in finance's court. [21:22:23] 06Team-Practices, 10TPG-FY2016–17-Q1-Improve-Annual-Planning, 07Epic: [EPIC] Support Annual Planning retrospective activities - https://phabricator.wikimedia.org/T138241#2394543 (10Awjrichards) [21:27:59] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey: Determine new SOP for Light Engagement survey - https://phabricator.wikimedia.org/T141138#2488318 (10KLans_WMF) * What it is * How to send it * How to process it ... [21:34:00] 06Team-Practices, 10TPG-Essential-Functions: Support Finance in creating and communicating a budget review process - https://phabricator.wikimedia.org/T142596#2650479 (10ggellerman) [21:41:04] 06Team-Practices, 10TPG-Essential-Functions, 10TPG-FY2016–17-Q1-Identify-Common-Pain, 07Epic: [EPIC] Provide support to people in design-related roles - https://phabricator.wikimedia.org/T137479#2650498 (10Awjrichards) [21:41:06] 06Team-Practices, 10TPG-FY2016–17-Q1-Identify-Common-Pain, 07Epic: [EPIC] Identify and address a common pain point across teams we interact with. - https://phabricator.wikimedia.org/T139630#2650496 (10Awjrichards) [21:41:09] 06Team-Practices, 10TPG-FY2016–17-Q1-Identify-Common-Pain: Report on findings so far on effort to address common team pain point - https://phabricator.wikimedia.org/T140939#2650494 (10Awjrichards) 05Open>03declined We get this for free with quarterly reviews; killing this now in favor of that. [21:41:58] 06Team-Practices, 10TPG-Essential-Functions, 10TPG-FY2016–17-Q1-Improve-Annual-Planning: Facilitate annual planning retrospective focus groups - https://phabricator.wikimedia.org/T138244#2650503 (10ksmith) a:05Awjrichards>03ksmith [21:44:46] 06Team-Practices, 10TPG-FY2016–17-Q1-Improve-Annual-Planning: Prepare for annual planning retrospective focus groups - https://phabricator.wikimedia.org/T138243#2650537 (10ksmith) a:05Awjrichards>03ksmith [21:45:54] 06Team-Practices, 10TPG-FY2016–17-Q1-Identify-Common-Pain, 07Epic: [EPIC] Identify and address a common pain point across teams we interact with. - https://phabricator.wikimedia.org/T139630#2650549 (10Awjrichards) [21:45:56] 06Team-Practices, 10TPG-FY2016–17-Q1-Identify-Common-Pain: Share rationale for deciding on selected pain point - https://phabricator.wikimedia.org/T140931#2650547 (10Awjrichards) 05Open>03declined Get this for free with quarterly review; killing this task in favor of that [21:48:22] ggellerman: do we need to meet tomorrow to get the multiple wave b survey forms created and ready, or do you have that under control? [21:49:04] i think that with recent developments that we should prob meet tomorrow [21:49:14] warning: not alot of whitespace already [21:50:03] ggellerman: any chance you could ping abbey or dario to see if they go the CSAT today? I bumped a couple people but haven't heard back [21:50:30] subject was: "Feedback wanted by 9/19: Team Practices Group Q1 Survey (shorter and updated!)" [21:50:34] Dario is at a conf, but will try to get a DR team member to let me know...stay tuned [21:53:01] kristenlans: JMo confirms receipt of email [21:53:21] ggellerman: excellent - paranoia mitigated [21:55:09] kristenlans: yay! [21:58:45] ggellerman: good job finding an open slot! (as always, many of my meetings are negotiable) [21:59:25] ggellerman meeple27 what's the best way for me to send you a list of folks for the light engagement survey? also, what is the timing expected on that - is it worth also including the stakeholders going through the validation sessions or is it too early for that? [21:59:48] awjr: I can privately im you the doc to drop them into [22:00:02] timing for wave b is: opens wed, closes a week later [22:00:33] ok then probably should hold off on the stakehodlers [22:00:37] besides that's a really big group [22:00:39] (aka closes 9/28, which is probably roughly as late as you could go to get good data into quarterly review decks) [22:01:15] you could technically do your own wave at any time, but ideal would be after 10/5 to incorporate any feedback from round 2 [22:01:48] feedback = lessonings about the survey itself [22:02:34] lol [22:02:45] i <3 gerrunding [22:12:48] yeah, I used to enjoy verbing, but gerundings are the new best thing [22:30:31] ggellerman: Do you feel strongly that the "what we learned about the survey" should go on [the same | a different] wiki page as/from the "what we learned from the survey" that you posted? [22:31:08] meeple27: I do not feel strongly on this one. I leave it with you :) [22:31:53] Ok. I fully appreciate and support your indifference, and will...gasp...make a decision [22:32:24] btw, I just linked to those results from https://www.mediawiki.org/wiki/Team_Practices_Group/Light_engagement_survey (which I had forgotten existed) [22:32:37] meeple27: I am aggressively indifferent ;) [22:45:18] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2650779 (10ksmith) [22:45:51] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10ksmith) [22:46:39] 06Team-Practices, 10TPG-FY2016–17-Q1-Roll-Out-Engagement-Survey: Report on Light Engagement survey 2nd round - https://phabricator.wikimedia.org/T141144#2650785 (10ksmith) [23:00:55] 06Team-Practices, 10TPG-Essential-Functions: Define TPG "light engagement" - https://phabricator.wikimedia.org/T133560#2650832 (10ksmith) Our working definition of "light engagement" seems to be "any work TPG does for others that is not part of an embedded assignment". Suggested possible names for work falli... [23:17:28] 06Team-Practices, 10TPG-Essential-Functions: Define TPG "light engagement" - https://phabricator.wikimedia.org/T133560#2650884 (10ggellerman) @ksmith Of the options you propose, I like "Engagement." Might we also benefit from defining what "embedded" means?