This working group is charged with rolling forward from the emergency "Engineering Allocation" prioritization methodology to a new process. The working group should name, design, kickoff, implement, solicit feedback, and iteratively improve the new process before disbanding. The new process should accomplish three major things:
|Target End Date||2023-01-31|
|Google Doc||Working Group Agenda|
|Issue board||Issue board|
|Open merge requests for the working group||MR list|
|OKR||Mature cross functional prioritization model|
|Overview & Status||See Exit criteria below|
Note that these goals are aspirational so we set a high bar (and potentially achieving something that is good enough vs. setting a low bar and not achieving something that is good enough).
The below criteria will be marked as complete when we close the working group, as we will be doing this iteratively until then.
We're phasing the rollout of the remaining exit criteria. This approach limits the surface area of changes to a single stage allowing us to rapidly iterate and reduce the churn of changes on all of R&D.
Phase 1: Create Completes all Exit Criteria by the September Create PI Review
As part of Phase 1 we'll actively review input and feedback from Create. Primarily Darva Satcher (Dir of Eng), Sarah Waldner (Create GPM), Marcel van Remmerden (UX Manager), and Ramya Authappan (QEM) and iterate prior to moving to Phase 2.
Phase 2: Roll out to every stage/section by October PI reviews Essentially all of phase one, including any iterations for all stages/sections.
Note: This does not preclude other stages beyond create to complete the exit criteria prior to October. Many teams are self-activating. For example, Wayne has activated Secure and David has asked all of PLT to begin to adopt this for their PI reviews. We'll focus the working group's energy in phase one on Create.
|Working Group Role||Person||Title|
|Executive Sponsor||Ashley Kramer||Acting CTO|
|Facilitator||Justin Farris||Senior Director of Product Management|
|Functional Lead||Wayne Haber||Director of Engineering|
|Functional Lead||Christopher Lefelhocz||VP of Development|
|Functional Lead||Valerie Karnes||Director of Product Design|
|Functional Lead||Christie Lenneville||VP of UX|
|Functional Lead||Mek Stittri||VP of Quality|
|Functional Lead||David DeSanto||VP of Product Management|
|Functional Lead||Farnoosh Seifoddini||Head of Product Operations|
|Functional lead||Lily Mai||Staff Engineering Analyst|
|Functional Lead||Tanya Pazitny||Director of Quality Engineering|
|Member||Jennifer Li||Engineering Manager, Engineering Productivity|
|Member||John Hope||Engineering Manager, Plan:Product Planning & Certify|
|Member||Matt Wilson||Senior Product Manager, Secure|
|Member||Neil McCorrison||Frontend Engineering Manager, Secure|
|Member||Donald Cook||Engineering Manager, Plan:Project Management|
|Member||Cheryl Li||Senior Engineering Manager, Verify|
The process is documented in the handbook.
gl-product-leadershipin all merge requests to solicit feedback.
#developmentslack channels, and in the weekly engineering work in review document.
wg-cross-functional-prioritizationlabel to all issues and merge requests so they can be tracked