List of Projects MetPlus Client meetings Meeting 11 - 02/12/2016

Meeting 11 - 02/12/2016

Updated almost 6 years ago by Joao Pereira
  1. Retrospective on Sprint 10
  • Waffle stories completed during the sprint:
    • Fix company registration 'deny' modal(#178)
    • Company Registration update bug(#180)
    • Improve messages displayed while login(#181)
    • Interface to edit/Register all the users(#142#146, #182, #185)
    • Improvement on administration home page(#184)

  • Waffle stories worked on during the sprint:
    • Begun work on jobs management features (#173)
    • Add functionality to Job Seeker(#157)
    • Start working in the notification system(#186)
2. Questions for the client
  • The idea is that a site visitor who requests a company registration (registrant) may have entered incorrect information. The registrant cannot delete the registration, so he or she has to communicate to the agency admin to make changes on their behalf.

    Typical scenarios might be:

    1. The registrant entered an incorrect email (they will be told that they will receive a 'pending registration' email, and when that does not come they might realize their mistake). The agency admin will go in and fix the email address, at which point the registrant will receive the 'pending registration' email.

    2. The registrant enters the wrong EIN.  As part of the vetting process for a company registration request, the jobs agency discovers this discrepancy.  After confirming the mistake with the company contact, the agency admin corrects the EIN and the rest of the approval/deny process can then proceed.

    The other approach to these problems - if we cannot update a registration request, is for the agency admin to simply delete any problematic request and ask the registrant to reenter the registration request. 

    At this point, we have already built the capability for the agency admin to edit the company registration record, as described in the above two scenarios.  The question at this point is: do we remove this capability or retain it?  (if we remove it, the only way to correct a "bad" registration is to have the registrant re-enter it.)

  • The way people actually use (or want to use) software once they have it is often very different from what was planned. So it is best to compare actual to imagined use as soon as possible.

    We are very close to having enough of the application working in order to do this. Would it be possible to do a small trial with a few job seekers and case manager? 

  • How are applicants supposed to apply for jobs? What is the process?

3. Questions from the client

4. Priorities for next sprint ( sprint 11, starting Monday, 02/14/16 )
  • Continue the user profile edit feature (user can edit their user attributes - e.g., phone, email, name, password, etc.)
  • Add "show" and "delete" capability for JobSeeker
  • Continue development for jobs management
  • Continue research on Notification system
5. Schedule next client meeting for 02/26/2016 at 5.30pm EST

comments powered by Disqus