2019 archive

Demo: September 11

Agenda Demo: client event logging — admin view Demo: event logging — ”hook” architecture Walkthrough Event logging hook architecture What work remains? Client event tracking refinements PIN validation on input Client sets their password, if not set CSV import to generate users, properties, RAVA requests, emails. Refined dashboard for “RAVAs all done” state. As a user, I can handle multiple properties. Reminders to Clients? »

Demo: September 18

Agenda Team: discuss import big picture Demo: import client records Deep dive: technical Q&A session Import big picture What are we doing? We are importing current client records and their associated property records, from the Access database that runs PAMS, who have an active appeal on a property, for 2020 appeals, who have not submitted the newly required RAVA. Piotr will create scripts that will generate the necessary CSVs for import in Nov/Dec, and import other counties in bulk later. »

Demo: September 25

Agenda Discuss: lead form Demo: import client records // signatory feature Demo: import property records Discuss: PINS Deep dive: technical Q&A session on primary keys, foreign keys Demo: client signatory import feature https://sc-portal-staging.herokuapp.com/imports/new If the primary contact record has ‘signator’ checked, import the secondary contact information instead Demo: import property records Discuss: PINs Would you want to know if the client reports PINs differently than what PAMS currently has them? »

Demo: August 28

Agenda Demo: Client experience: from invite, to completion, and password reset Demo: Admin printable view of submitted form Discuss: client event tracking and logging Discuss: Admin account shadowing Demo Walkthrough Note: Actual email delivery is a background job. Staging job runner only wakes up once an hour to not burn up free dyno time (production is every 10 minutes). To have jobs run immediately for demo, spin up a one-off dyno: heroku run rails jobs:work -a sc-portal-staging and quit when you’re done »

Demo: August 21

Agenda Demo: completed Client confirmation view Demo: Admin view of submitted RAVA forms Demo: prototype, Client email invitation Review MVP from June 26; review current MVP Review product vision, determine next steps Minimum Valuable Product: Final Sprints MVP: Minimum Valuable Product What’s the minimum valuable product? ✅ Admins generate a RAVA form request to a Client, for a property. ✅ Clients receive an email request to fill out a RAVA form. »

Demo: August 14

Agenda Demo: completed client ‘dashboard’ of buildings; form progress bar; action buttons Work completed this week Developed state indicator for forms progress bar Adjusted layout for buildings / progress dashboard Feedback PINs should be validated Building button labels: start, edit, view Add a confirmation view of the submitted form After a form is confirmed, client can’t delete it »

Demo: August 7

Agenda Demo: prototype, add, name, delete buildings; RAVA form. »

Demo: July 31

Agenda Client/buildings stories Client/buildings UX Client/buildings use cases ✅ CREATE: When I start the process, I want to add one or many buildings, so I can fill out a RAVA form for each of them. ✅ NAME BUILDING: When I’ve added a building, I want to name it, so I can easily refer to the building while filling out the RAVA form. ✅ UPDATE NAME: when I’m working on the building forms, I may want to update the building name, so that the name better represents the buildings I own. »

Demo: July 24

Agenda Portal Remote demo: client buildings — Buildings work in progress Resolution Partners project brief approved 16 July, sent to Pickleman Org Name: is there an LLC, Inc. associated with it? »