Fulfillment Provision Team
Vision
For more details about the product vision for Fulfillment, see our Fulfillment page.
The Provision group manages the Provision category.
Team members
Bishwa Hang Rai
Lukas Wanko
Mohamed Moustafa
Ragnar HardarsonStable counterparts
| Name | Role |
|---|---|
 Corinna Gogolok
|
Staff Backend Engineer, Fulfillment:Provision |
 Costel Maxim
|
Senior Security Engineer, Application Security, Plan (Project Management, Product Planning, Certify), Create:Source Code, Growth, Fulfillment:Purchase, Fulfillment:Provision, Fulfillment:Utilization, Systems:Gitaly |
 Courtney Meddaugh
|
Product Manager, Fulfillment:Provision |
 Divya Mahadevan
|
Fullstack Engineer, Fulfillment:Provision |
 Paulo Barros
|
Senior Backend Engineer, Fulfillment:Provision |
 Qingyu Zhao
|
Senior Backend Engineer, Fulfillment:Provision |
Project management process
The Provision project management process inherits from the general Fulfillment project management process and adds a few additional elements specific to the work that the Provision team does.
Planning
The milestone planning process is built around planning issues for the milestone, these issue outlines what issues will be worked on in the upcoming milestone, how those issues are prioritized, commentary on how that fits with over arching goals, and how the proposed work fits in the capacity for the next month. The Provision team use this template for it’s planning issues.
Planning Timeline
The team Engineering Manager and their Product Management counter part are responsible for implementing the milestone planning process. To complete all of the preparation work needed for each milestone the Provision team uses a schedule of:
- 1st of the month create new planning issue, ensure team member monitoring availability calendar is filled in for the upcoming month
- 9th of the month request engineer input and refinement of candidate issues
- 13th of the month finalized PTS and Sentry monitoring schedule
- 14th of the month final capacity planning for refined issues
- 18th of the month milestone starts
Refinement
The refinement process aims to ensure that all planned work can be completed within the scheduled milestone. During the refinement phase issues are distributed to engineers to answer three questions:
- Are there any open questions that prevent this issue from being marked as
workflow::ready for development? - Are there any design problems that could lead to predictable blockers coming up while implementing this issue?
- What weight estimate would you give for this issue?
Clearing foreseeable blockers helps to ensure that all scheduled work can complete without stalling. If there are issue that can not be completed due to design considerations those should pushed back to a future milestone to ensure capacity is directed to issues that can be delivered in the upcoming milestone. Having accurate estimates of the work needed for planned issues is important to ensure that all planned work can be completed accounting for team capacity.
Capacity Planning
The Provision team is primarily a development team, however given the nature of the team’s work there are additional operational concerns that routinely take team member’s time away from purely development tasks. The main recurring tasks that take team member time are:
- Monitoring the Provision Tracking System
- Monitoring Sentry for integration related errors
- Triaging licensing issues impacting customers
To account for the time consumed by the on going operational processes for each milestone a issue with a weight of 3 is created for Sentry monitoring and assigned to the engineer that is DRI for that process for milestone. For Provision tracking monitoring 4 issues with a weight of 1 each are created and assigned to engineers based on the Provision Tracking Monitoring schedule for the milestone.
The target weight for issues closed during a milestone is 0.5 * (Total number of working days accounting for time off). There is an open issue discussing ways to move to planning capacity to a per engineer granularity.
Change Management
In the spirit of Iterationand Collaboration these processes are a work in process. Suggestions on improvements or new processes to try can be proposed under this epic.
Historical capacity
Points of weight delivered by the team on the last milestones. This allows for more accurate estimation of what we can deliver in future milestones. Full chart to be migrated.
Performance Indicators
### Provision #### Top Engineering Metrics dashboard #### MR Types dashboard #### Development dashboard #### Infrastructure dashboardDashboard
Dashboard
Dashboard
Dashboard
OKRs
The Engineering Manager will report on the progress of OKRs every two weeks. Current OKRs: FY22-Q1
4e6ac4e3)
