Case Management Digital Service Sprint Review€¦ · CWDS / Child Welfare Digital Services Case...
Transcript of Case Management Digital Service Sprint Review€¦ · CWDS / Child Welfare Digital Services Case...
CWDS / Child Welfare Digital Services
Case Management Digital ServiceSprint ReviewSprint 4.1: 8/24/17 – 9/6/17
Agenda
• Sprint Stories• Sprint Backlog• Team Metrics• Research, Design, & Business Presentation • Design Operations Presentation• Development Presentation• What's Next
Stories• Business
• Lassen County Site Visit• Communications Planning & Strategy
• Research and Design• Lassen County Site Visit• LA County Site Visit• Research Synthesis• Communication & Logistics Planning• Bi-weekly County Call Strategy• CoDesign Workshop Exploration + Strategy• Continued work on design system process + prototype
• Development• Development Infrastructure Progress• Choosing the Stack • Configuring Docker and Jenkins• Updated styles from Intake & Cals• Versioning process defined• Distribution Process of Component Library
#1 Team Stories
Sprint Metrics Sprint 1 Sprint 2 Sprint 4.1Iteration 1 2
Planned Capacity % / PTS 85% / 136 86% / 145
Accepted # of Planned Feature Stories / PTS 46 / 128 43 / 124
# of Completed Feature Stories / PTS 46 / 128 43 / 124
% Completed (by PTS) 94% 86%
# of Stretch Backlog Features / PTS 1/2 0/0
% Completed (including Stretch, by PTS) 94% 86%
Average Velocity over 3 sprints 128 124
Cycle time for Features (in hrs.) 93 136
#1 Team Metrics
What we learned
Case Management Researcher Antoinette Houston, CUAmapping the Emergency Placement workflowonsite with Social Workers in Lassen County.
Research & Design and Business
In-Person Discovery with ExpertsRESEARCH & DESIGN and BUSINESS
OUR APPROACH• Round table discussions with key
Lassen County staff• Rich 1-on-1 + group dialogues w/
workers across Intake, ER and RFA specialities
• A series of interactive workshop “gaming” activities
Case Management Researcher Antoinette Houston, CUA performing onsite “gaming” activities with Social Workers in Lassen County.
OUR FOCUS To understand + learn:
• The Lassen County Emergency Placement (EP) workflow
• Worker efforts used to find family and other NREFM during EP
• Identified collaborations, handoffs & challenges
Case Management Research + Business team prepping for workshop.
WHAT WE DISCOVERED• Lassen County EP Insights• Growing similarities and
differences between Lassen and other counties researched thus far related to Emergency Placement efforts
Experience Map highlighting consolidated county experiences: YUBA, L.A. & Lassen
Designing WITH, not for...RESEARCH & DESIGN and BUSINESS
Codesign Workshop in SacramentoDate: 9/21-9/22
Initial in-person workshop serves as a jumping-off point
Fun, engaging activities
Design Operations
Visual Design DirectionDESIGN OPERATIONS
CONSIDERATIONS
● Information Architecture
● Product Personality
● Accessibility Standards
EXPECTATIONS & NEXT STEPS
● Continuous feedback loop
with core counties
● Iterate accordingly
● Mobile design strategy
Component Library ToolsDESIGN OPERATIONS
WHERE WE ARE
• Static Generated Style Guide/CSS (Hologram)
• NPM Distribution from react-wood-duck
• Tested Fractal, Catalog, and React Styleguidist
WHAT’S NEXT
• Dynamic Living Style Guide (Fractal)
• Extend NPM and SASS support
• Potentially explore Storybook
• Merge with react-wood-duck
DevelopmentCase Management
Choosing the StackDEVELOPMENT
Dev Box
VPN
DEVELOPMENT
Balance:
Team Strengths + Platform Norms + Goodness of Fit
Choosing the Stack
react-rails
Dev InfrastructureDEVELOPMENT
Build Box
Dev Box
Docker Configuration to Support Jenkins
Using Jenkins and Docker developers can push new features to users within minutes or hours of completion instead of weeks or months.
• Configured Dockerfile to build the docker image.
• Tested Docker image to check whether all devs can run this image successfully.
• Before doing continuous integration, we have setup a sample application for testing
• The Dockerfile and .dockerignore available at URL: https://github.com/ca-cwds/case-management/tree/hello-world.
• Identified Common Styles from INTAKE & CALS
• Added Styles and updated the component library with bumping patch version
• Defined versioning process• Coordinated with
Wood-duck(DesignOps) on contributing components to pattern library
Global UX Pattern LibraryDEVELOPMENT
Retrospective
What went well:There was a lot of resonance with the team about being able to separate Dev and Design in Pivotal Tracker.
Improvement Opportunity:Top item identified was being proactive with PI4 planning
Carry over retrospective item was realistic capacity.
ImpedimentsTeam Control – We are working to overcome the challenges related to creating cohesive, mutually supportive team that integrates a government business team and 2 vendor teams.
Team Influence – Staffing timeline for TPT is forcing some adjustments in planning.
Organizational – Staffing timeline for Product Owners and Testers.
What's Next?• Continue User Research with Core Counties• Co-design Workshop - 9/21/17 and 9/22/17• Test & Verify the Development Environment • Automate the Deployment Process• Continue working on the Strategy for the Prototype• Continue to build reusable common components across digital
services
Reminders:Agile Training - 9/7/17, 9/27/17, 10/12/17Bi-Weekly County Call - 9/13/17, 11:00-12:00Case Management Sprint Review - 9/20/17, 2:30-3:30
Questions?
Appendix