MVP fields for initial application

[lippytak]

I think MVP should have ability to write to these fields in the application PDF:

• Name (pg 7 of PDF)
• Address (pg 7 of PDF)
• Home phone (pg 7 of PDF)
• Email address (pg 7 of PDF)
• Email comms consent (pg 7 of PDF)
• Signature (pg 7 of PDF)
• Date (pg 7 of PDF)
• Interview preference day/time (pg 8 of PDF):
• Notes...not exactly sure if we need to write anything here but maybe we could say "submitted via OUR-KICK-ASS-WEBSITE" or something (pg 6 of PDF)

[daguar]

Just want to do a quick peer gut-check -- would you consider these truly the minimal, viable fields?

[lippytak]

Damnit, you're right. Answer is no. Here's the incremental value:

1. Name legally required
2. Address legally required
3. Signature legally required
4. Date legally required (but can be auto-populated with current date?)
5. Phone # high value so first post-application contact can be phone instead of postmail
6. Email medium value so first post-application contact can possibly be email instead of phone
7. Interview day/time preference ambiguous value...depends if first contact is a phone call to schedule an appointment or letter with already scheduled appointment time.
8. Email text/consent consent required iff we're decide to email or text
9. Notes low value...only suggested

So in summary, #1-3 are MVP user inputs, #1-4 are MVP fields printed on application, and #1-5 is my benefit >>>> cost judgment.

[daguar]

1-6 has been implemented on the back end (i.e., what can get written by the Calfresh application generator library) so I'm going to pause new fields until the front end is at MVP.

[daguar]

What info?

On Apr 30, 2014, at 12:49 PM, Jake Solomon notifications@github.com wrote:

Not suggesting we add this for MVP, but Leo mentioned they might need more information to

— Reply to this email directly or view it on GitHub.

[lippytak]

Mistake. Ignore this. Was starting to writeup something about DOB and how CF "clears" new cases, but that's best left to a later convo with Leo.

On Wed, Apr 30, 2014 at 12:52 PM, Dave Guarino notifications@github.comwrote:

What info?

On Apr 30, 2014, at 12:49 PM, Jake Solomon notifications@github.com wrote:

Not suggesting we add this for MVP, but Leo mentioned they might need more information to

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/daguar/calfresh-and-so-clean/issues/2#issuecomment-41842116 .

[daguar]

Want to add DOB? Pretty trivial.

On Apr 30, 2014, at 3:30 PM, Jake Solomon notifications@github.com wrote:

Mistake. Ignore this. Was starting to writeup something about DOB and how CF "clears" new cases, but that's best left to a later convo with Leo.

On Wed, Apr 30, 2014 at 12:52 PM, Dave Guarino notifications@github.comwrote:

What info?

On Apr 30, 2014, at 12:49 PM, Jake Solomon notifications@github.com wrote:

Not suggesting we add this for MVP, but Leo mentioned they might need more information to

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/daguar/calfresh-and-so-clean/issues/2#issuecomment-41842116 .

— Reply to this email directly or view it on GitHub.

[daguar]

I'm closing this issue -- please reopen if there are additional fields that are for the MVP/demo. Otherwise, we can open issues for additional fields later.