To help ensure consistency, team collaboration, visibility and best practices across all HP web platforms.

  PO BA UX Design UI Design UX Research Accessibility UX Engineer Developer Content Specialist Copywriter
Component intake (tracking in JIRA) C C C C C C R/A C C C
Ensures component requirements are well defined A R C C C C C C C C
Ensures component brand guidelines are met I I C R/A I C C I I I
Component library maintainance (bitbucket/git) I I I I I I C R/A C I
Design Library maintainance (site build) I I C C I C R/A C I I
Updates to component status/information in Design Library C C C C C C R/A C C C
Creates user testing process C C C C R/A C I I I I
Creates and maintains accessibility guidelines I I C C I R/A C C C I
Creates and enforces accessibility testing processes C C I I I R/A C C C I
Creates and enforces component intake process R R R R C C R/A R R R

UI Design:

  • Accessibility has been consulted and addressed
  • Development has been consulted
  • Deliverable: Design specs have been completed for L, M, S and XS views including development requirements
  • Deliverable: Any new assets are ready to hand off to development for build (e.g. system icons, sample imagery, etc.)

UX Design:

  • Solution/component solves the business need/problem/opportunity
  • Solution/component is usable (See UX Research below)
  • Solution/component is unique and does not replicate existing component
  • Solution/component is socialized cross product to ensure reusability for all/most products for uniform alignment
  • Solution/component is socialized with UI Dev to ensure buildability and maintainability
  • Still noodling on format here and other items (Jeff K).....

Development:

  • The component...
    • has a Jenkins pipeline instantiated for executing static scans (ESLint, Fortify, etc.) and deploying to Nexus (and eventually Artifactory).
    • has unit tests and all are passing.
    • has completed a peer code review.
    • is responsive.
    • demonstrates that functionality works in all supported browsers and devices.
    • meets current accessibility standards.
    • has "live" documentation (something like "Storybook" where all of the attributes are documented, and the components are displayed / modifiable).
    • is bug free, or, if approved, known bugs are added as stories to the Vanguard board in Jira.
    • has source code in the "Component Library" repo in Bitbucket - http://git.healthpartners.com/projects/HPPL/repos/component-library/browse/hppl
    • The Jenkins pipeline has been executed (code passes all static analysis scans and is deployed to our artifact repository).

BA:

  • Component request has been completed
  • Story created design library JIRA
  • Use cases, requirements & design specifications are defined
  • Component meets accessibility requirements 
  • Component passes QA & UAT

Content Specialist:

  • Component has been approved by all other disciplines
  • QA has been completed for character counts, all screen sizes, accessibility, brand alignment, etc.
  • Component is ready to be authored
  • Design and development are aligned
  • Component exists in Design Library

User Research:

  • The component needs to have been included in at least one usability study
  • The component needs to comply to UX best practices

When requesting a component be added to the Design Library, please download complete the Design Library request form as detailed as possible and send it to patternlab@healthpartners.com

Once we receive the request it will get added to the Design Library JIRA backlog and reviewed by the Design Library Governance Group.

The Governance Group will look over the request and ensure it meets all new component criteria. If the group determines the component does not work on a global, scalable, sustainable or brand level we will work with the requesting team to revise the component. If the component being requested is similar to another component we have already built, we will suggest using the current component or updating it to meet the new use case requirements.

This group is not an approval process for project work, rather it is a way for us to increase visibility to the work being done and create re-usable components. We will work with teams to help ensure scalability and consistency across projects. 

Once the group determines the component is viable, it will be tracked through the Design Library JIRA board as your team specs and builds it out. Your team is not responsible for updating this board, only providing us the completed information for each stage. There are 7 stages we will track: 

Backlog: This is where all components start, regardless if they end up getting approved. Components that are not approved wil stay here and can be revisited in the future.

In process: The in process stage means the component is moving along in definition and wireframes/UI mockups.

Ready for Development: The team has completed requirement definition, use case, specifications, design. (send the requirement doc - Confluence link preferred - and UI mockups)

In Development: The component is being built in the Component Library. (send link to Bitbucket component)

In Component Library: The component has been filly built and tested in the Component Library and is ready for implimentation.

Needs Update: This column is to track any components that are currently in the Design Library but have been identified as having an issue or are being updated. 

In Design Library: The team has completed the component and it has been consumed by Design Library. All necessary information has been provided.