June 2019 Agenda - hackforla/311-data GitHub Wiki
Team Roll Call
Running Roll Call:Date: 06-25-19
Agenda:
- Administrative setup of github repo
- Wiki
- Analyze actual 311 data and determine if correlations can be drawn
- "Can we actually make this work"
- Ideate other 311 visualization tools
- Find existing neighborhood council initiatives
- https://data.lacity.org/A-Well-Run-City/MyLA311-Service-Request-Data-2019/pvft-t768
Notes:
- Internal data analysis tool to help find correlations with 311 data -- year over year, month over month, etc.
- Deploy on Raspberry Pi
- Pull data when it detects internet
- Frontend Dashboard
- Backend DB with data
- Startup script
- JSON 311 dataset for 1 year = 500mb
Next Steps:
- Talk tech stack
- Implementation?
Date: 06-18-19
Agenda:
Review readme doc content and format
Deciding how to document roll call, then doing roll call
- Will document roll via Google Sheets @ 311-Data Roster
Deciding how to do skills inventory, interest, and then doing it
- Russell Tan: Mobile frontend (swift), Backend, AWS/platform
- Winston Laoh: Backend, test, tools, infra engineer, project management
- Joshua Marx: Frontend, UI/UX(Storytelling)
- Armett Johnson: Frontend, UI/UX, product roadmapping
- Harsh Bhatt: Back-end engineer
- Lauren Sandberg: Product/project management, UX, product roadmapping
- Nathan Daneilsen: Frontend, UX, Product roadmapping
Skeleton roles and responsibilities
- Product Owner/Manager
- Interfaces with and represents the customer
- Determines product requirements and roadmap
- Communicates needs/requirements/goals with the rest of the team
- Project Manager
- Resource negotiation with DTLA HackforLA hosts
- Communicating with tech/UI/UX leads to establish feasible requirements
- Draft agenda, run meetings
- Set/speak to tech milestones
- Tech Lead
- Act as voice for reasonable delivery timelines, communicate tech lift involved
- Responsible for overall system architecture
- Perform code review
- Drive QA standards
- UI/UX Lead
- Represents the user
- Designs interfaces, user flows
- Performs user/usability testing
- Communicate with tech lead to ensure they're on the same page about capabilities
- Customer/Stakeholder
- Communicate their needs/goals (for product, and for timeline)
- Review prototypes, User Acceptance Testing
- Commitment
Review
- Current My311-bi: https://empowerla.org/demographics-BI/
- Mayor's Dashboard 311 request intake site: http://dashboard.lamayor.org/
- LAEmpower site: http://empowerla.org/
Are there any other 311 visualization tools?
- My311 Data repository: https://data.lacity.org/A-Well-Run-City/MyLA311-Service-Request-Data-2019/pvft-t768
- NYC 311 Data: http://people.ischool.berkeley.edu/~samuel.goodgame/311/
- https://cvalenzuela.github.io/alt_docs/found_materials/
Next steps?
- Need to hear back from EmpowerLA re: neighborhood council reps!
- Ideate other 311 visualization tools
- Discuss skills and responsibilities