The Data-Engineering team is going through a process of re-organizing the workboard, which has, over the years, accumulated a large volume of open, stale tickets. As a part of this process, a large fraction of the existing Analytics tasks will be temporarily moved to this new Data-Engineering-Icebox tag as a holding area.
Many moves to this tag will be based on the team's evaluation and reconsideration. Regardless of the mechanism, moves of tasks from Analytics to Data-Engineering-Icebox are not intended to be any reflection of any personal or team opinion on the validity or importance of a given task. We aim to reduce the main Data Engineering workboard to active, ongoing work and current incoming issues. After the initial removal of many tasks to the icebox (from June 9th to June 23rd, 2022), we will be re-organizing the columns of the main workboard into a more Sprint-inspired workflow, and we will also be doing a one-by-one human triage process on all icebox tasks during planning.
This one-by-one triage process will include:
- Reviewing for the need to move tasks back to the primary Data Engineering workboard (caught up in bulk filters or hasty imprecise decisions)
- Categorizing the tasks into Icebox columns by their nature (new features/decline/Not a priority but nice to have).
- Pinging stakeholders (author, assignee, and/or others) for updates or resolution (or, in some rarer cases, closing immediately when it seems clear this wouldn't be controversial or contended by stakeholders).
- Un-tagging (from analytics) for tasks managed by other (sub-)teams on other boards, where Data Engineering doesn't have any significant stake or role in the task.
At the end of this first pass of triage, most of them are expected to remain open in the Icebox for some time. The Icebox is not intended to be a graveyard! Over the next two quarters, we'll look for new ways to organize some of the ideas and requests captured in many of these tickets.