Page Comparison

...

...

...

We use a centralized-ish governance model.

...

...

Design and engineering work is federated.
Decision making is centralized.

The three Part-time Paragon Leads act as owners and facilitators. They partner with designers and engineers via the #paragon-working-group to determine and the weekly Paragon Working Group Meeting to coordinate work and make decisions on the direction of the librarysystem. Engineering work

Work is cataloged on the Paragon Jira backlog Backlog by Paragon Leads and the Experience Team and . Work is completed primarily by Engineering Squads in the course of their work .Project owner: Adam Butterworth (Deactivated) and through blended development initiatives lead by the Paragon Leads.

...

Part-time Paragon Leads

...

• Who: Designers on the Experience Team

• When: Create or update components as use cases arise in squad work

• Responsibilities:

  • Bring their proposals to the Paragon working group for review and acceptance

  • Create a Jira ticket in the Paragon backlog and notify the engineering squad they work with.

Engineering Implementation

...

Who:

• Status
  colour Blue title primary

  Squad Engineers

• Status
  colour Yellow title AD HOC

  Contractors via blended development
  There is no active blended work scheduled or in progress

• Status
  colour Red title Sparingly

  Adam Butterworth (Deactivated)

...

When:

• Squad engineers: pull in or copy Paragon tickets for components needed to complete their work.

• Contractors: Ad hoc, no current plans

• Adam Butterworth: teams reach out for help and he has bandwidth

Responsibilities

...

Implement the design spec referred to by the Jira ticket

...

Paragon Working Group

The Paragon Working Group is an informal group of volunteer engineers and designers who meet weekly at the Paragon Working Group Meeting and discuss issues in #paragon-working-group Slack.

Roles and Responsibilities

Product Lead

• Supports the strategic direction of the system

• Aids in chunking of work in Jira

• Supports blended development initiatives

• Serves as a champion and advocate among product leaders.

Technical Lead

• Directs the architectural roadmap

• Implements the architectural direction: individually, via blended development, or may escalate to theme leadership to assemble a tiger team.

• Ensures incoming Paragon bugs are triaged and resolved, as needed

  • Leveraging time from the working group to triage and support the design system.

• Helping to facilitate Paragon Working Group meeting

• Ensures engineers are supported in contributing to Paragon

• Ensures pull requests are reviewed in a timely manner. Any frontend engineer at edX is permitted to perform code reviews at the discretion of the

  Status
  colour Green title technical owner

  .

• May implement new component designs when appropriate

Design Lead

• Drives the design direction of the system.

• Supports designers using and contributing to Paragon

• Helps to facilitate Paragon Working Group meeting

• Fixes or improves design documentation

• Triage and resolve design bugs

Paragon Working Group

• Provides feedback and approval on proposed design additions, technical additions, and architectural changes

• May also assist with the responsibilities of the design owner and technical owner

• Participate in a support and triage rotation to continue to maintain the design system.

Engineering Squads

Writing and maintaining UI components is a core part of User Interface Development. We want to foster and encourage a culture of writing components needed by a given team, to a standard level of maturity, and then introducing those components directly into the Paragon ecosystem for sharing and re-use.

This development should be done in tandem with, and under the design and technical guidance of the design team and Paragon Technical Owner to ensure that components are as mature and effective as possible.

• Squads are responsible for the development of components they need.

  • If a squad does not have the frontend expertise to build a component that they need, they should escalate the need to their theme leadership. We recommend that each theme should have at least one frontend expert. Other options for development include: blended development or negotiation with other squads.

• Reviews pull requests. Any frontend engineer at edX is permitted to perform code reviews at the discretion of the

  Status
  colour Green title technical owner

  .

Squad Designers

• Identify needed components in the course of squad work

• Design and document new or updated components or design system features in Figma

• Support engineers building components and design system features from specs in Figma

• Identify Paragon components and design system features used in design specifications