The Progressive Delivery (PD) group is focused on all the functionality with respect to Continuous Delivery and Progressive Delivery.
You can also reach out to the Progressive Delivery Slack channel #g_progressive-delivery.
For in progress design work see the following page.
Other pages of interest:
TODO: Auto add list of epics and important issues up ahead based on labels.
Our planning and build process is detailed on our planning page.
Progressive Delivery works with monthly and quarterly planning issues using the release planning issue template to plan our release-level priorities over each milestone. These issues contains individual sections for deliverables, capacity, team member vacation, and more. This issue allows the entire group to view high-level planning including what we seek to accomplish in a given release. This type of issue is the central location for information gathering and planning conversations.
Planning issues are considered SSOT until they are closed as the milestone has begun. After that, the issue metadata is the leading SSOT. Additionally, Progressive Delivery honors items in the current milestone over scheduled future milestone items.
Needs weight issues are used by engineering to dedicate
workflow::planning breakdown activities. If an issue has no weight it should preferably first pass through a needs weight issue to be assigned a weight. Afterwards it can be proposed in the planning issues. Additionaly, Product Design can indicate in these issues by the use of this issue board where there is an additional need for engineering involvement to push forward issues in the
For our past planning content see the archive.
TODO: Add Progressive Delivery competitive analysis epic
You can view and contribute to our current list of JTBD and job statements here.
When situation I want to job so I can outcome.
|When situation I want to job so I can outcome.||Issue|
TODO: Detail exactly how we work from a UX PoV
OKRs stand for Objectives and Key Results and are our quarterly objectives. We work to achieve the company OKRs by contributing towards stage OKRs. Achieving these goals will advance us towards product maturity in the categories linked above.
|Objective: Measure our success through consistent delivery||
|Key Result: Delivery on all issues outlined in the Q3 quarterly epic||
|Key Result: Have a positive Say/Do Ratio of 70% at the end of Q3||
|Objective: Reevaluate the maturity of the Continuous Delivery Product category||
|Key Result: Create a JTBD overview of the Continuous Delivery product category and have this detailed in the handbook||
|Key Result: Complete a maturity scorecard for Continuous Delivery||
|Objective: Improve GitLab performance, quality, and velocity by making GitLab development Pajamas first by covering Progressive Delivery related issues||
|Key Result: Migrate Vue instances of buttons and pagination to Pajamas for Progressive Delivery||
|Key Result: Migrate Vue instances of dropdowns, modals, and tabs for Progressive Delivery||
|Key Result: Migrate Vue instances of popovers and tooltips to Pajamas for Progressive Delivery||
|Key Result: 100% of new features in GitLab Progressive Delivery added in Q3 use Pajamas components||
For our past OKRs see the archive.
|Objective: Improve GitLab performance, quality, and velocity by making GitLab development Pajamas first||
|Key Result: Migrate Vue instances of buttons and pagination to Pajamas||
|Key Result: Migrate Vue instances of dropdowns, modals, and tabs||
|Key Result: Migrate Vue instances of popovers and tooltips to Pajamas||
|Objective: Improve UX MVCs by providing iteration training to all designers||
|Key Result: Effectively apply iterative design principles||
|Objective: Scale UX Research to improve velocity and participation||
|Key Result: 80% of new studies in Q3 utilize the ~"Actionable Insight" label (both Problem and Solution Validation)||
For our past OKRs see the archive.
For recordings see our Release (CD) UX YouTube channel.
TODO: Integrate DoD process into PD
View our Product Performance Indicator.
Learn more about UX Debt in the UX Department Performance Indicators page.
The Progressive Delivery stage group commits to having at least one UX Debt and one UI polish issue scheduled per milestone at minumum.
The Progressive Delivery stage group triages both UX Debt and UI polish issues alongside Bugs to signify if something is severe for our user experience. UX debt is already officially triaged across the company. Our triage reports are optimised with lists and heatmaps having this usecase in mind.
TODO: Auto link directly to last triage report issue