Core Platform Team/FY1819 Closeout

Overview and purpose
As we approach the conclusion of the current year, our objective is to compile a comprehensive list of all ongoing initiatives. Subsequently, we aim to establish a definitive 'completed' status for each project that we can attain by July 15th, 2019. This entails making strategic decisions, which might involve trimming the scope of certain projects, temporarily shelving others, or potentially reassigning them to the Clinic Duty segment of our project planning board. For each endeavor, it's imperative that we set an attainable target, allowing ourselves the mental bandwidth to transition smoothly into the upcoming year.

Guidelines:

If you're engaged in a project not enlisted here (or if the project is reactionary and involves intermittent engagement), please document it below. For every project, draft a clear definition of what 'completed' entails. This should encompass actionable and tangible tasks, either documented or within Phabricator. Be courageous in proposing a plan! For each project's definition of 'completed,' also devise a level of accomplishment that renders the project viable for temporary closure and future revival. (While resuming these projects immediately in the new year is a possibility, we require a definition of accomplishment for FY 18/19.) Identify any risks or dependencies tied to each project that warrant resolution. Allocate two sign-off columns for each project: one for a Technical Lead/Engineering Manager and another for a Project Manager. If the 'completed' column is well-formulated and feasible, kindly affix your endorsement. In cases where project scope is reduced but necessitates continued efforts after July 15th, kindly generate a project ticket on our Asana project board. This will facilitate its scheduling. On July 1, 2019, the leads will jointly review and finalize this consolidated list.

Additional Implicit Points:

EMs/Tech Leads and PMs are encouraged to collaborate and arrive at a consensus regarding 'completed' criteria. If feasible, convene a meeting to discuss the projects. If you're already serving as the PM, EM, or Tech Lead for a project, you should ideally be involved in defining the 'completed' parameters. At a minimum, your endorsement is valuable. While unlisted, coordination with other team members is implicit. You're expected to liaise with engineers as necessary. Efficiency is key – existing project scopes likely contain the requisite details; focus on retaining essential components."

Feel free to adjust this as needed or let me know if you'd like further assistance! As we approach the conclusion of the current year, our objective is to compile a comprehensive list of all ongoing initiatives. Subsequently, we aim to establish a definitive 'completed' status for each project that we can attain by July 15th, 2019. This entails making strategic decisions, which might involve trimming the scope of certain projects, temporarily shelving others, or potentially reassigning them to the Clinic Duty segment of our project planning board. For each endeavor, it's imperative that we set an attainable target, allowing ourselves the mental bandwidth to transition smoothly into the upcoming year.

Guidelines:

If you're engaged in a project not enlisted here (or if the project is reactionary and involves intermittent engagement), please document it below. For every project, draft a clear definition of what 'completed' entails. This should encompass actionable and tangible tasks, either documented or within Phabricator. Be courageous in proposing a plan! For each project's definition of 'completed,' also devise a level of accomplishment that renders the project viable for temporary closure and future revival. (While resuming these projects immediately in the new year is a possibility, we require a definition of accomplishment for FY 18/19.) Identify any risks or dependencies tied to each project that warrant resolution. Allocate two sign-off columns for each project: one for a Technical Lead/Engineering Manager and another for a Project Manager. If the 'completed' column is well-formulated and feasible, kindly affix your endorsement. In cases where project scope is reduced but necessitates continued efforts after July 15th, kindly generate a project ticket on our Asana project board. This will facilitate its scheduling. On July 1, 2019, the leads will jointly review and finalize this consolidated list.

Additional Implicit Points:

EMs/Tech Leads and PMs are encouraged to collaborate and arrive at a consensus regarding 'completed' criteria. If feasible, convene a meeting to discuss the projects. If you're already serving as the PM, EM, or Tech Lead for a project, you should ideally be involved in defining the 'completed' parameters. At a minimum, your endorsement is valuable. While unlisted, coordination with other team members is implicit. You're expected to liaise with engineers as necessary. Efficiency is key – existing project scopes likely contain the requisite details; focus on retaining essential components.

Inflight projects
Below is the list of projects we are working on that we wish to get to some state of "done" before we start the work for next year.