Blog Post Week 14

Status Report for Week 14

Tasks accomplished

1. Completed User Testing
2. Analyzed and reviewed test results

Tasks In Progress

1. Create Final Presentation
2. Update project package for final release

Tasks Planned For the Next Two Weeks

1. Finish the above tasks

Issues

1. Group coordination: Some of the team has not been invested in the project, missing deliverables and not being able to respond promptly to other group members.

Metrics

1. Team
1. Group meetings to talk about user testing and coordinate final delivery (1 hour)
2. Analyze results (2 hours)
3. Work on presentation (2 hours)
2. Mike
1. User Testing (2 hour)
3. Richard
1. User Testing (2 hour)
4. Jeremy
1. User Testing (2 hour)
2. Interface work (2 hours)
5. Bill
1. Interface work (2 hours)
6. Total: 47 hours

Blog Week 12

Status Report for Week 12

Tasks accomplished

1. Set up environment for the prototype.
2. Rough prototype
3. Getting users to accept in testing the system.

Tasks In Progress

1. Refinement of the prototype, as there wasn't much functionality to the prototype thus far.
2. User Testing Start

Tasks Planned For the Next Two Weeks

1. User Testing of the prototype
2. Update test plan 
3. Analyze test results

Issues

1. Group coordination: Some of the team has not been invested in the project, missing deliverables and not being able to respond promptly to other group members.
2. Adapting to new technology: As the prototype was created with only two members, another member has been helping with the set up of django, and there have been some issues involving setting up the project environment, but those have been resolved as of now.

Metrics

1. Team
1. Group meetings to talk about user testing and coordinate the creation of pages (3 hours)
2. Work on prototype (2 hours)
2. Mike
1. Configure version control and coordinate communication between the team (3 hours)
2. Help with issues of setting up environment (1 hour)
3. Richard
1. Set up environment (1 hour)
2. Talk with users (1 hour)
4. Jeremy
1. Set up environment (1 hour)
2. Talk with users (1 hour)
5. Bill
1. Set up environment (1 hour)
6. Total: 32 hours

Blog Week 8

Status Report for Week 8

Tasks accomplished

1. Met with team to start work on setting up our project environment (team, 1 hour)
2. Started learning about bootstrap and the other technologies we are going to use (individual, 2 hours)
3. Recruited additional users for user testing (individual, 1 hour)
4. Created test plan for the project (team, 3 hours)

Tasks In Progress

1. Create the system prototype/beta according to previously determined requirements

Tasks Planned For the Next Two Weeks

1. Finish the system prototype/beta
2. Heuristic evaluation notes
3. Potentially begin user testing

Issues

1. An issue with working knowledge of our testing environment required us to do some research about it. 
2. We have only had three of our members participate in group meetings, and have had no input from our fourth member in a number of weeks. 

Metrics

1. Team
1. Test Plan (3 hours)
2. Set up our environment (1 hour)
2. Richard
1. Recruit Users (1 hour)
2. Learn about our technologies (2 hours)
3. Jeremy
1. Recruit Users (1 hour)
2. Learn about our technologies (2 hours)
4. Bill
1. Recruit Users (1 hour)
2. Learn about our technologies (2 hours)
5. Total: 18.5 hours

Week 4

Status Report for Week 4

Tasks accomplished

1. Met to work on and complete the SRS document (Whole team, 2 hours)
2. Created individual HTAs, and collaborated with the team (1 hour, individually)
3. Finished rough prototype (1 hour, team meeting, and individual time)

Tasks In Progress

1. More fleshed out prototype

Tasks Planned For the Next Two Weeks

1. Elicit users and gather information (each person responsible for 1, half an hour - 1 hour)
2. Design Document (3-4 hours)
3. Conceptual prototype (2 hours)

Issues

1. Scheduling with different classes and projects has been difficult, but we have resolved these issues for the most part, and have found a time for most of the team to meet together. 
2. Differing views on the prototype, has been resolved by working together on the project as a team. 

Metrics

1. Team
1. SRS (2 hours)
2. Richard
1. HTA (.5 hours)
2. Add on prototype (.5 hours)
3. Jeremy
1. HTA (.5 hours)
2. Add on prototype (.5 hours)
4. Bill
1. HTA (.5 hours)
2. Add on prototype (.5 hours)
5. Mike
1. HTA (.5 hours)
6. Total: 5.5 hours

Week 2 Post

This week our team accomplished most of the Deliverable 1 SRS document, spending around 3 hours in a team meeting to do so.
The next week we will finish up Deliverable 1 as a team, we think it will take about 1-2 hours.
The only risks, challenges and issues our team faces so far is somewhat spotty team meeting attendance by some team members.

Features Post

Team Cosmonaut

Richard Ngo

Jeremy Vasta

William Spaw

Michael Kenworthy

Tasks Accomplished:

Initial project chosen from list of project proposals - The group came together and picked the Study Group Finder as the project to work on. The Study Group Finder will be a web application that will help students K-12 form study groups, based on subjects they’re having trouble with.

Feature List -

Students

• The ability to create a profile, with a username, password, name, grade, location, email, list of teachers, availability, and list of subjects that help is needed with.
• An option to show matches with the students schedule, subjects, location, and grades, showing both individual students and groups that match the criteria.
• The ability to join groups and create new groups

Teachers:

• The ability to create a profile with a username, password, name, email address, and list of students
• The ability to facilitate groups for students

Groups

• A group will have a name, a list of students, a subject, a schedule, meeting location, a bulletin board, and a resource repository

Future Tasks:

- Recruit four users for next week - Each member of the team will look for 1 or 2 users to recruit - Start on deliverable 1 - The group will work on this together

Risks, Issues, and Challenges:

- Deciding on a final project to work on. We had not decided on an idea until late in the week, as there were pros and cons to each of the project proposals.

- Scheduling was difficult for the team as we were unable to find a time for the whole team to meet