- Time logging solution for Quincy Library tutors from Literacy Volunteers of Massachusetts.
- Jeremy Clark — Product Owner and Dev team member
- Joshua Coffie — Scrum Master and Dev team member
- Muhammad Abdullah — Dev team member
- Ian Hoffmann — Dev team member
- Jason Reed — Dev team member
- Carnic — Dev team member
Connect Literacy Program participants so that they can share achievements, document their efforts, and cultivate friendships within the adult learning community
- Provide an administrative interface for program coordinators to analyze participant activity and generate reports
- Allow participants to register for membership to the site
- Offer a user-friendly interface for tutors to log student activity
- Provide an administrative interface for program coordinators to analyze participant activity
- Program Administrators
- Tutors
- Students
****** Click here to view the user Persona PDF v2 ******
- Molly is the Program Administrator
- She is 40 years old
- Patient, passionate, charismatic, fun
- Has spent most of her life in the educational services field, focusing on ESL and international education
- Traveled to Spain in college to learn Spanish, traveled to Costa Rica to teach at an English School
- Her primary device is a Windows Laptop
- Her mobile device is an iPhone 6
A little bit more about Molly:
She is a full-time mother of two with a passion for helping people. She finds immense fulfillment in teaching ESL at the local library while balancing duties at home. She builds relationships quickly, preferring to hand-make cards for people rather than buy them, builds lifelong friendships working alongside adults teaching them English, stays up late to take care of her family, and insists that she makes plenty of time in her day for her kids to garden and teach them about life.
Her frustrations with the current system:
- Repetition/inefficiency of tasks
- Making sense of raw data
- Limitations on data filtering
- Lengthy technology interaction
The key aspect of backlog ordering we took into account over all others was MVP. This is expressed through our choice to put the main time-logging functionality ahead of most other non-core backlog items. Initial comps of the product was chosen as the most important backlog item, because giving the stakeholders an idea of how the product will look and function is of great value to them. Some of the items at the bottom of the project backlog are there because of dependencies and non-essential functions. Nevertheless, they constitute functionality that would be appreciated by stakeholders. All in all, MVP, dependencies, stakeholder involvement, and time constraints played the largest factor in ordering the backlog to its current condition.
Copyright (c) 2016, Team Rosetta and Harvard University, CSCI S-71 Agile Software Development
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.