List view
Mostly code maintenance tasks and cleanup that were ignored due to "end of semester rush". - Refactoring - Documentation in app and on GitHub - Making easily distributable to those reading a research paper :)
Overdue by 10 year(s)•Due by December 31, 2015Assuming the research ends and the project is not endorsed (read: purchased), then this is (almost) the end. If they do purchase, figure out strategy for continued maintenance. Implement any last minute changes and make sure it is stable and working for the residents.
Overdue by 10 year(s)•Due by December 19, 2015- Work with the partnering facility to review the application if they choose to own it. Make sure to adhere by corporate standards and guidelines. Try to get branded application logos and splash screens and other client specific touches.
Overdue by 10 year(s)•Due by December 5, 2015Finish up all implementation considerations that couldn't be completed in 0.7. This is a lot of HARD STUFF.
Overdue by 10 year(s)•Due by November 14, 2015A major focus on backend development will happen in this release so that it can be built so it can run officially for the partnering facility. This will lay the groundwork for, but not complete: - resident data security - securely grabbing resident info in realtime (and hopefully caching?) - the workflow for adding a new resident to some system allows front-desk staff to add them to the application
Overdue by 10 year(s)•Due by October 31, 2015By this time, major usability changes should be coming through in order to address the findings from data collection in the field. This will be important as the paper will be starting soon.
Overdue by 10 year(s)•Due by October 17, 2015This should begin to take into account usability changes based on initial field testing responses. Most of this will be informally gathered. Continued work can be done on the data and back-end layers of the application.
Overdue by 10 year(s)•Due by October 3, 2015I anticipate that this version should begin to include real resident data for testing. While this will not mean that a whole database and server backend will be implemented within this time, at the very least I should look into methods that will allow for easy export of their current directory data into something that can then generate the JSON that is powering the app.
Overdue by 10 year(s)•Due by September 26, 2015•0/3 issues closedThis will include implementations of changes from the partnering IL/AL facility that they will likely suggest upon our first meeting. This will not move back in due date and the timeboxing will be firm.
Overdue by 10 year(s)•Due by September 12, 2015•1/7 issues closedWill be used to address all usability issues and unpolished aspects that were ignored in the original 0.1 prototype. Upon completion, this will be a "demo"-able product for a facility.
Overdue by 10 year(s)•Due by September 7, 2015•19/21 issues closed