14.3 Optimize planning

%14.3 Planning for groupoptimize

• Board link: https://gitlab.com/groups/gitlab-org/-/boards/1401511?milestone_title=14.3&&label_name[]=group%3A%3Aoptimize

---

%14.3 Milestone: 2021-08-18 to 2021-09-17

Capacity

Please add your PTO and order by From date

Person	From	To
@wortschi	2021-08-16	2021-08-22
@blabuschagne	2021-09-XX	2021-09-XX (~ 3-4 days in Sept)
@ogolowinski	2021-08-22	2021-08-24
@ogolowinski	2021-09-06	2021-09-08
@ogolowinski	2021-09-15	2021-09-16

Training

Person	From	To
@ahegyi	2021-08-30	2021-09-03

Objectives

1. Improve the reliability of VSA so it works the way customers expect and we can grow adoption
2. Burn down security issues

Themes

• Performance
• Security
• Usability
• OKR

Title	assignee	Weight	Theme	Priority
Confidential	@pshutsin	2		High
Confidential	@blabuschagne	1		High
Confidential	@ekigbo	1		High
[DevOps Adoption] Page constantly refreshes	@blabuschagne	1		High

Research/Needs Weight ‍♂️

Defining Success

To-Do

• Define an approximate scope for the coming release.
• Apply appropriate labels to issues:
  • Priority
  • Department
  • Pricing Tier
• Review the proposed scope with Engineering.
• Review design objectives with UX.
• Get feedback and estimates from Engineering, confirming scope for the release.
• Final verification of issues scheduled for the release.
• Present selected issues in the Manage Kickoff on the 17th!

Previous <= => Next

changed milestone to %14.3

added Planning Issue devopsmanage groupoptimize sectiondev labels

changed the description

It would be great to schedule gitlab-org/gitlab#337256 (closed) if we have capacity. It has been causing some customer confusion.

@gitlab-org/manage/optimize Here is the planning issue. Please add anything you think we need to focus on for 14.3

changed the description

changed the description

changed the description

Adding the adoption table to the Overview tab - 3

Change the refresh behaviour for the devops adoption page - 1

Add a note about refresh times in devops adoption - 1

Add lead time for change to group-level VSA

Is this frontend only?

Stage tab should only show data for selected projects

This was fixed in %14.1 along with gitlab-org/gitlab#330314 (closed)

Improve project deselect behaviour in VSA

changed the description

@wortschi @ljlane Are we managing the security effort here as well or should it be added to the Access planning issue?

@ogolowinski I do think that we should add them to the Access planning issue. We do use two separate boards during out weekly call to track progress on security and on Optimize work.

@ljlane WDYT?

@ogolowinski We've been adding the security work to the Access planning issue and keeping a mental note that we're aiming for 5 points for Ezeikel and Brandon, which is 50% capacity, for the Optimize planning issue. That seems to be working fine for now.