Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

General Information

Daily Stand-Up: Noon Eastern time, https://zoom.us/j/3935010675

Sprints:

  1. Nov. 30 - Dec. 18
  2. Dec. 21 - Jan. 14
  3. Jan. 15 - Feb. 4
  4. Feb. 5 - 25

Some Documents:

Questions

First Discovery Tool Construction Sprint Requirements

 from: https://docs.google.com/document/d/1p88RZghb4sDjn0aUi8bRMo5booy4rC-Di11t2pwQHBs/edit

  1.  Integration with the GPII Preferences Server
    1. Requirement All-2: KeyToken & Save
      1. "The tool(s) must, at the start of the process, create a KeyToken (e.g., NFC, USB, etc.)". This seems like it is out of date, as we now create a preference set with the selected preferences at the end of the process. A cookie is used to store the FD Tool's state and the users selected preferences locally. The system can be restarted using the ctrl-option/alt-r keyboard command.

Other

  1.  When will the functional tests (QA) take place? What is needed for this?
  2. Is the tester from the Technical Development Team also part of the "Tool Evaluation Team"? If not, will he be available to help with the functional testing?
  3. Who will perform this "construction" goal: "Where feasible, perform any ICT and Assistive Technology enhancements necessary at the chosen sites"?
  4. How are we assessing whether or not a site meets the criteria of necessary range of user needs? I don't see any questions to this end in the survey or otherwise. Suggested potential question wording: (Dana working on it)
  5. Are we including an evaluation of the ease of integration in the overall usability testing? I think we should. Need to consider usability test questions for integrators.

  • No labels