designops sprint review - amazon web services · designops sprint review sprint 9.1 august 24 -...
TRANSCRIPT
DesignOpsCWDS
place image here
DesignOps Sprint ReviewSprint 9.1 August 24 - Sept 5
Research
● CANS 1.0 User Feedback
Design
● Associations & Relationships Concepts
● RFA - Accept & Return Applications after Submission
Sprint Activity
DesignOps Sprint Review 2
Research
place image hereCompleted
● 19 user feedback sessions with demos● 21 participants from El Dorado, Lassen, Los Angeles,
Merced, and Sacramento counties
In-progress: Analysis Sept 3-7● Feedback session notes analysis● Feedback session screencast review (18 hours of video)
Next steps: Synthesis Sept 10-14● Mental Health Data Alliance’s CANS Focus Group
findings● CWDA feedback notes● Final findings document delivery Mon Sept 18
4DesignOps Sprint Review
CANS 1.0 User Feedback (WIP)
Design
place image here
● Create Association Design Concept in collaboration with SMEs
● Research & Identify “Association Type” categories with SMEs
● Create phased approach for transitioning from Legacy Relationships to Future People Associations
● Collaborate and share Associations concepts w/SMEs, Product Owners, and Service Managers for feedback
● Evaluate CARES impacts on data needs & features with Future People Associations data
6DesignOps Sprint Review
Associations &Relationships
place image here● Outlined the workflow from an RFA Draft through the Successful Acceptance of an RFA Application
● Introduced Pop Over Menu and Modal UI solutions to CALS
● Collaborated with SMEs and Core County Stakeholders on these design concepts
● Delivered annotated screens for development reference
● Repurposing screens to support other RFA focused user stories moving forward
7DesignOps Sprint Review
RFA - Ability to Accept & Return Applications after Submission
Design System
place image here
What’s Next? (from last time)
● SaaS integrations with ca-cwds/design-system
● Components○ Form Elements○ MultiContext Card
● Sourcing Additional Technical Resources (e.g.; JS & QA)
$ diff sprint todo’s
+ Integration Path+ MDX Documentation
- SaaS integrations+ Guide Content+ Field Label Standards
Components- Form Elements- MultiContext Card+ DataGrids
Library Status Tracking
Changelog
---------
* (guide): Add DataGrid async examples (#29)
* (components): Add DataGrid component (#25)
* (guide): Moar MDX content plz
* (components): fix Toggle Btn Color (#28)
* (guide): fix InfoTip/Tooltip examples
* (guide): Update Labs area
$ lerna ls
@cwds/components v0.2.0-alpha.14
v0.2.0-alpha.16
@cwds/core v0.1.0
@cwds/validation v0.0.1
design.cwds.io v0.1.0 (private)
rails_app v0.1.0 (private)
Integrating @cwds/components (Piecewise vs All-at-Once)
● Reduce Delivery Risk● Product Teams:
○ Set their own pace○ Smaller Velocity Discontinuity
Technical Considerations:
● CSS Module Packing● ES Module Imports Big Namespaces● Tree-Shakable again
Collections
There is not a consistent implementation in CARES for “collection” interactions
● List Management● Master:Detail● Collection Views● Set Membership
Let there be <DataGrid />!
<Demo />
place image here
What’s Next?
● DNS● Components
○ Form Elements○ MultiContext Card
● Add Technical Resources
Questions?