This table we are using comes from Team Practices -- see https://www.mediawiki.org/wiki/Wikimedia_Engineering/OKR

I had an interesting conversation with @RobLa about these objectives and about defining objectives in general. He says that in general we need to have shorter lists of objectives at a team level, in order to decrease / focus the list of WMF objectives. He used/improvised an interesting way to know when a task should should or should not be marked as objective: would you be absolutely embarrassed if that objective would not be completed by the end of the quarter?

I actually like this definition a lot. The current list is full of interesting / important / urgent tasks, but it is true that failing in some would be more embarrassing than failing in others.

Please think about this, and let's aim to stamp a team approval on this list by our team meeting next Tuesday.

PS: and just to be clear, we will always work on more tasks than the ones defined by our objectives, but we can track those through task priorities and monthly sprints. What is clear is that we should not fail embarrassingly with our official objectives because at the end we got busier with the not-so-important tasks that we could have postponed a bit without embarrassment.

As per last comment I removed the "Gerrit cleanup" item because I would not feel embarrassed enough.

The impact of goal (was key results) should define "How will success be measured - Quantitative measures
SMART." A measurable outcome.

T93584 and T94166 have measurable outcomes defined. The other three goals... not so much, or maybe I'm not seeing them. @Spage, @Aklapper, let's discuss and agree how are we going to measure success, latest by the end of our team meeting today.

About Dependency, what is expected is "Department - Dependency Description - Quantitative where possible". These are external dependencies, people out of ECT. Please be concise, you can always expand on details in the related task.

I edited my two items (external deps) but I have a hard time to come up with quantitative measures for a task that is basically about creating quantitative measures.

After the reorganization announced yesterday, we need to look again to these goals. Many things are still in flux, so I will not rush to change these goals, but let's see:

• T93584: the hackathon driven by @Rfarrand is still the main goal and absolutely nothing changes there.
• T307: dev.wikimedia.org is now up in the air, both because @Spage is now in another team (still discussing his current role) and also because the priority of this project needs to be reassessed. Unless something changes in the next weeks, we will drop this goal for this quarter.
• T87470: a new Architecture team has been created as part of a new CTO department, which is a reason good enough to deduce that little ECT does not need to own this task anymore. I propose to remove this task from the goals now.
• T94166: GSoC and Outreachy are not affected at all by this reorg, and @NiharikaKohli in her role as volunteer org admin stays also the same.
• T94578: Lila told us explicitly that we need to deliver these metrics in future quarterly reviews, and even if @Aklapper is today in another team, his role and duties haven't changed a bit. I propose to keep the goal and owner untouched.
• T96013: I'm happy to work on this but first I want to check with Kourosh Karimkhany (new VP of Strategic Partnerships) if / how this goal fits in their goals. Leaving it here for now.

Please confirm or propose better ideas.

In T93770#1206907, @Aklapper wrote:

I edited my two items (external deps) but I have a hard time to come up with quantitative measures for a task that is basically about creating quantitative measures.

"Metrics agreed implemented and published by the end of the quarter."?

In T93770#1227115, @Qgil wrote:

• T307: dev.wikimedia.org is now up in the air, both because @Spage is now in another team (still discussing his current role) and also because the priority of this project needs to be reassessed. Unless something changes in the next weeks, we will drop this goal for this quarter.

In fact, I just removed it as a goal. The tasks are still open and associated to the current sprint, but we cannot sanely commit for this goal in this qarter when right now we don't even know whether S will have any time to work on this. Let's continue discussing #dev.wikimedia.org in the context of sprint planning and the main tasks.

• T87470: a new Architecture team has been created as part of a new CTO department, which is a reason good enough to deduce that little ECT does not need to own this task anymore. I propose to remove this task from the goals now.

Done.