This Week:
This week a lot of the usability errors that were found during the heuristic evaluation. Thanks to our use of the functional prototype we got really good feedback and all comments were made on a product that could be the final user interface with some polishing.
We have been focusing on getting ready for the actual testing and team members have been trying to get more users to include in our testing plan.
Overall:
Task: Readme/Product prototype release
People involved: All team members
Hours: .5 hrs per team member
Task: Product
People involved: All team members
Hours: 0.2 hr per team member
We have been focusing on getting ready for the actual testing and team members have been trying to get more users to include in our testing plan.
Task: Readme/Product prototype release
People involved: All team members
Hours: .5 hrs per team member
Task: Product
Next Week:
Next week we will need to focus on finalizing the users, and making sure that everything is ready before we test. Also, it will be important to get the login system done before we test so we can get feedback on it.
Challenges, Risks, and Issues:
Challenges:
Our team has been finding it extremely difficult to find users. Due to our app being applicable to anyone from the ages of 5-18 we have a large range of both computer and math competence. We realize that we will only be able to test on a limited subset of our users, but still worry about complete user demographic coverage. Unfortunately due to the current situation (being in college) of all the members on the team, we don't really know anyone from the area that is in our user demographic.
Risks:
We are still encountering the same risk as last week, where as the semester is speeding up team members may re-prioritize classes/other activities ahead of this project. This is still being mitigated by getting early starts on deliverables and continuing to have weekly team meetings regardless if the deliverable is due that week.
An additional risk arises because of two main factors - team members are becoming busier and more focused on other classes and projects, and we are completing work for this project more and more on an individual basis. We run into a risk that a section of some document may reference a new or updated feature or design that the rest of the team is unaware about. We are attempting to mitigate this by finding time to read or glance over each others sections and putting personal responsibility on updating others if an issue arises.
An additional risk arises because of two main factors - team members are becoming busier and more focused on other classes and projects, and we are completing work for this project more and more on an individual basis. We run into a risk that a section of some document may reference a new or updated feature or design that the rest of the team is unaware about. We are attempting to mitigate this by finding time to read or glance over each others sections and putting personal responsibility on updating others if an issue arises.
No comments:
Post a Comment