Page MenuHomePhabricator

[Epic] FY 2022-23 Growth Maintenance Work
Closed, ResolvedPublic

Description

This epic captures maintenance work the Growth team will focus on during the FY 22-23 (July 2022 - June 2023).

Maintenance tasks relate to:

  • Refactoring to enhance reusability and manageability of the codebase.
  • Extension maintenance (community facing or internal) and updates.
  • Technical organization initiatives that fall outside product work e.g. major migrations
  • Tasks that fall outside of ongoing product epics and those belonging to epics that been complete for more than 3 months(This is long enough to not count as follow up work post deployment).

Details

Due Date
Jul 1 2023, 10:00 PM

Related Objects

StatusSubtypeAssignedTask
OpenNone
ResolvedNone
OpenNone
Resolvedkostajh
In ProgressBUG REPORTNone
DeclinedVolker_E
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
In ProgressNone
Resolvedkostajh
Resolvedkostajh
OpenNone
OpenNone
DeclinedSgs
ResolvedTgr
InvalidNone
ResolvedNone
ResolvedSgs
ResolvedTgr
Resolvedkostajh
ResolvedSgs
ResolvedEtonkovidova
ResolvedNone
Resolvedkostajh
Resolvedkostajh
OpenNone
ResolvedKStoller-WMF
Resolvedkostajh
ResolvedTgr
Resolvedkostajh
OpenNone
Resolvedkostajh
ResolvedUrbanecm_WMF
ResolvedSgs
ResolvedUmherirrender
DeclinedNone
DeclinedNone
ResolvedSgs
In ProgressSgs
OpenNone
ResolvedFeaturekostajh
OpenNone
OpenNone
OpenNone
OpenBUG REPORTNone
OpenBUG REPORTNone
OpenBUG REPORTNone
OpenBUG REPORTNone
OpenNone
StalledDMburugu
ResolvedTgr
OpenSgs
OpenNone
ResolvedNone
ResolvedTgr
In ProgressNone
Resolvedmatmarex
Resolvedkostajh
OpenNone
OpenBUG REPORTNone
OpenNone

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

@DMburugu @MShilova_WMF is there an epic task for Q2? (Maybe we should make an epic task for the fiscal year, then link each quarterly epic task underneath it, for discoverability?)

By my count, we got through 9 out of 53 tasks added in Q1, so ~17%. I am not sure what percentage would be reasonable to target, but 17% feels like we didn't complete as much as we hoped to.

@kostajh , this is a great point. To be honest, given how ambitious the workload of the Growth Team is, I suggest getting rid of the notion of quarterly maintenance epics and just renaming this epic to FY 2022-23 (track the maintenance work for the whole fiscal year). What do you think?

CC: @DMburugu

@kostajh , this is a great point. To be honest, given how ambitious the workload of the Growth Team is, I suggest getting rid of the notion of quarterly maintenance epics and just renaming this epic to FY 2022-23 (track the maintenance work for the whole fiscal year). What do you think?

CC: @DMburugu

I prefer to keep quarterly epics (and ideally monthly epics too) so we can more realistically plan and hold ourselves accountable to things we want to do. A yearly epic would end up being a very long list that would be hard to prioritize/triage, IMHO.

MShilova_WMF renamed this task from [Epic] Q1 FY 2022-23 Growth Maintenance Work to [Epic] FY 2022-23 Growth Maintenance Work.Oct 13 2022, 4:25 PM
MShilova_WMF updated the task description. (Show Details)

@kostajh , I did the following:

In my opinion, monthly epics are overkill for our team. We are not really moving at a very high pace when it comes to maintenance. However, I don't have a strong opinion. I just would like to avoid unnecessary administrative work.

Sgs changed the status of subtask T324549: Increase Vue coverage from Open to In Progress.Dec 15 2022, 12:07 PM
Aklapper set Due Date to Jul 1 2023, 10:00 PM.Jun 26 2023, 5:05 PM
KStoller-WMF moved this task from Inbox to Triaged on the Growth-Team board.

@DMburugu - I'm cleaning up Growth's current sprint. Let's move any open tasks that are still higher priority to: T340453: [Epic] FY 2023-24 Growth Maintenance Work. Thanks!

Sure. Will this be the norm moving forward?

Sure. Will this be the norm moving forward?

You are welcome to manage this however you and Growth engineers think is best; I just think we should limit the number of open epics in our current sprint.

FY 2022-23 ended three months ago. Should this task be closed?