List of Projects MetPlus Client meetings Meeting 19 - 06/03/2016

Meeting 19 - 06/03/2016

Updated over 5 years ago by Patrick Bolger
Retrospective on Sprint 18

1. Waffle stories completed during the sprint:
  • Job Seeker search Jobs (#100)
  • Build interface with "cruncher" to pass job for parsing, characterization and comparison (that is, "job matching") (#288)
  • Job match result page and design of résumé-matching display (e.g., five star rating system (#296)
  • Add list of applied jobs to Job Seeker landing page (#223)
  • Display applied jobs (by job seekers) to Job Developer home age (#228)
  • Assign job_skills to a job (#268)
2. Other Waffle stories worked on during the sprint:
  • Agency person home page
    • List all job seekers without a Case Manager (#234)
  • Code reuse and UI improvements on Agency Person Landing page (#314)
3. Questions for the client
  • Feedback from the Landing pages review
  • Feedback from the search page functionality
4. Questions from the client

5. Priorities for next sprint ( sprint 19, starting Monday, 06/06/16 )

  • Delivery of most or all stories listed above in "stories worked on during the sprint"
  • Agency Person Home page enhancements (Code reuse and UI improvements)
  • Job Management system continued development, e.g.
    • Job life-cycle states (active, revoked, filled)
    • Allow company person and agency personnel (JD) to set status
  • Continue working on "job matching" features, for example:
    • Job seeker résumé match to jobs (show all matching jobs)
    • Job Developer matching job to job seekers' résumés (show all matching job seekers)
  • Other stories from the project backlog

5. Schedule next client meeting for 06/17/2016 at 5.30 pm EST

6. Action points from this meeting:
  • Feedback from client:
    • Improved search looks good and addresses the points he made at prior client meeting (see meeting notes from meeting 18).  Job search is now very flexible meets his needs.
    • Other demo'ed items look good.
    • Discussion on task management: when a task is marked as complete, it disappears from the view of the assignee.  Chet said that a user could click the "complete task" icon by mistake, and without having actually completed the task.  We talked about a few options to help with this, and ended up with these ideas for implementation:
      • If the next status change of a task causes it to disappear from view of the assigned user, there should be a dialog box to confirm that the task is, in fact, completed (and also tells the user that the task will disappear from their "pending tasks" table, and,
      • Provide a view of "completed tasks" so then user can keep track of completions, and also see information associated with a task that was incorrectly marked as completed (e.g., the specific job seeker that was to be assigned to the user as job developer).

comments powered by Disqus