For more details about the vision for this area of the product, see the Plan stage page.
This team is currently shared between Plan:Portfolio Management and Plan:Certify.
|John Hope||Engineering Manager, Plan:Portfolio Management & Plan:Certify|
|Felipe Artur||Backend Engineer, Plan:Portfolio Management & Plan:Certify|
|Jarka Košanová||Senior Backend Engineer, Plan:Portfolio Management & Plan:Certify|
|Jan Provaznik||Senior Backend Engineer, Plan:Portfolio Management & Plan:Certify|
|Charlie Ablett||Senior Backend Engineer, Plan:Portfolio Management & Plan:Certify|
|Annabel Dunstone Gray||Product Designer, Plan|
|Donald Cook||Frontend Engineering Manager, Plan|
|Fatih Acet||Senior Frontend Engineer, Plan|
|Kushal Pandya||Senior Frontend Engineer, Plan & Geo|
|Winnie Hellmann||Senior Frontend Engineer, Plan and Intern Backend Engineer, Plan|
|Amarbayar Amarsanaa||Senior Site Reliability Engineer, Create, Plan, Monitor|
|Rajat Jain||Frontend Engineer, Plan|
|Scott Stern||Frontend Engineer, Plan|
|Coung Ngo||Frontend Engineer, Plan|
|Walmyr Lima e Silva Filho||Senior Test Automation Engineer, Plan|
|Michal Wasilewski||Site Reliability Engineer, Create & Plan|
|Holly Reynolds||Senior Product Designer, Plan|
|Alexis Ginsberg||Senior Product Designer, Plan|
|Keanon O'Keefe||Senior Product Manager, Plan:Portfolio Management|
|Russell Dickenson||Senior Technical Writer, Plan|
This chart shows the progress we're making on hiring. Check out our jobs page for current openings.
We use a lightweight system of issue weighting to help with capacity planning, with the knowledge that things take longer than you think. These weights are used for capacity planning and the main focus is on making sure the overall sum of the weights is reasonable.
It's OK if an issue takes longer than the weight indicates. The weights are intended to be used in aggregate, and what takes one person a day might take another person a week, depending on their level of background knowledge about the issue. That's explicitly OK and expected.
These weights we use are:
|1||Trivial, does not need any testing|
|2||Small, needs some testing but nothing involved|
|3||Medium, will take some time and collaboration|
|5||Large, will take a major portion of the milestone to finish|
Anything larger than 5 should be broken down if possible.
We look at recent releases and upcoming availability to determine the weight available for a release.
To assign weights to issues in a future milestone, we ask two team members to take the lead each month. They can still ask questions - of each other, of the rest of the team, of the stable counterparts, or anyone else - but they are the initial. This is currently shared across the three Plan backend teams: Project Management, Portfolio Management, and Certify, so people will be asked to weight some issues outside of their immediate team.
To weight issues, they should:
The rotation for upcoming releases is:
|12.3||2019-08-07||Felipe Cardozo||Heinrich Lee Yu|
|12.4||2019-09-07||Charlie Ablett||Mario de la Ossa|
|12.5||2019-10-13||Brett Walker||Alexandru Croitor|
|12.6||2019-11-13||Jarka Košanová||Patrick Derichs|
|12.7||2019-12-13||Jan Provaznik||Eugenia Grieff|