PD 13.1 Planning Issue
🚀
Internal Milestone 13.1 Review & Discussion 13.1 Milestone: 2020-05-18 to 2020-06-17
🌴
Holidays Please order by From date
Person | From | To |
---|---|---|
Orit | May 28 | May 28 |
Nicole | May 25 | May 26 |
Chase | May 25 | May 25 |
Amy | May 25 | May 25 |
Jason | May 25 | May 25 |
Etienne | May 18 | May 18 |
Andrew | May 15 | May 18 |
Jason | June 1 | June 2 |
Amy | June 1 | June 1 |
📦
Capacity Last 3 Milestones: @csouthard to fill out
-
Average MRs completed: 12.9, 12.10, 13.0 ~= 25.333 MRs
-
Average MRs per Engineer: 25 MRs / 5 Engineers = 5 MRs/Engineer
Stats derived from here: https://app.periscopedata.com/app/gitlab/638154/WIP-Group::Progressive-Delivery
🔁
13.0 Spillover Priority issues (~"Release::P1") that didn't make the release cutoff:
- List of active ReleaseP1 issues => As of 2020-05-18, Current weight: ~= 21
Non-priority issues that didn't make the release cutoff:
- List of other active issues => As of 2020-05-18, current weight: ~= 13
🦊
Deliverables Top priority deliverables:
Issue | Weight |
---|---|
* Offer in-product guidance for deploying to AWS | 1 |
* Prepare our current Canary to support Canary-Weight ingress annotation | ? |
* Show alerts in environment index page | 2 |
Total weight:
Category | Weight |
---|---|
Spill P1 | 21 |
Spill Other | 13 |
New Deliverables | 10 |
P2/P3 Bugs | 4 |
Security | 2 |
50 |
P2 issues:
Issue | Weight |
---|---|
* Allow parent project's developers to create pipelines for merge requests for fork MRs | ?? |
🤝
Community Issues - Notifications for when pipelines are fixed => Need to determine team impact and how we should prioritize over existing issues
🕵
Research - Needs Weight Issue - gitlab-org/gitlab#215759 (closed)
🎢
User Experience Targets the main priority issues for active product design work. Preferably weighting the effort should already have been completed for these items!
Total UX weight per milestone |
---|
TBD |
Weighting uses the storypoints system |
Top priorities (P1):
Issue | UX weight | Status | Target milestone | Comments |
---|---|---|---|---|
Show alerts in environment index page (gitlab-org/gitlab#214634 (closed)) | workflowplanning breakdown | %13.1 | Top priority | |
Offer in-product guidance for deploying to AWS (gitlab-org/gitlab#207830 (closed)) | workflowready for development | %13.1 | Top priority | |
Notifications for when pipelines are fixed (gitlab-org/gitlab#24309 (closed)) | ~"workflow::In review" | %13.1 | Other priority | |
Cancel deployment jobs when there is an alert on an environment (gitlab-org/gitlab#216949) | ~"Dimi::In Progress" | %13.2 |
|
|
Allow parent project's developers to create pipelines for merge requests for fork MRs (gitlab-org/gitlab#217451 (closed)) | workflowdesign | BE possibly %13.1, FE possibly 13.2 | Other priority, but high priority for next milestone | |
Add cancel rollout button to the alerts page (gitlab-org/gitlab#219216) | ~"Dimi::In Progress" | %13.2 | Other priority, can be pushed out | |
Implement Blue/Green Switch on Deploy Boards (gitlab-org/gitlab#218140 (closed)) | 13.2 | Top priority | ||
Set deployment Traffic Weight via UI (gitlab-org/gitlab#218139 (closed)) | 13.2 | Top priority |
🕵
Research
Issue | UX weight | Status | Target milestone | Comments |
---|---|---|---|---|
A/B testing Problem Validation (gitlab-org/ux-research#676 (closed) ) | ~"Dimi::In Progress" | %13.1 | DRI: UX - Last touches discussion guide, recruitment should be started up | |
User Research for Post-deployment monitoring (continuous verification) MVC (#657) | %13.1 | DRI: PM - Looking for 2 new participants |
🐛
Bug Fixes Top bugs:
- Review Apps Environments for merge request branches are not stopped upon merge/reject
- Pipelines are linked to wrong MR on Merge Request page
- Duplicate instances in deploy board
Total weight: 8
🔒
Security Fixes Top security Issues:
💼
Technical Debt
🌵
User Experience Debt
🖌
User Interface Polish
🎯
OKR Alignment - Progressive Delivery Quarterly goal
- Product Manager complete 2 Validation Cycles - gitlab-com/Product#730 (closed)
- Product Manager completed projected Maturity
- Design OKR - Conduct 5 user research sessions for the UX Maturity Scorecard to evaluate the experience of Release Orchestration gitlab-com/www-gitlab-com#6201 (closed)
- Engineering OKRs (CI/CD)
👀
Things to Pay Attention To - Deprecate Legacy Feature Flags - if not done in 13.0, we will need to push this to 14.0
- Move features to core: "Feature Flags"
Planning Tasks
-
Team updates holidays section -
EM update capacity section -
PM highlights work for Deliverables, User Experience, Bug Fixes, Security Fixes, Technical Debt sections -
PM describes how this milestone aligns with our team's OKRs -
Team highlights Things to Pay Attention To section -
Engineers begin working on issues in workflow::ready for development
Edited by Dimitrie Hoekstra