Objectives
Understand the importance of end user feedback in development methodologies
Assignment
As part of the development methodology you will want to get end user feedback before a final implementation. This is a key tenet of Agile Development. You should fully read the Wikipedia article on Agile ( http://en.wikipedia.org/wiki/Agile_software_development ) and understand why it is a preferred methodology over other models (such as the traditional Waterfall Model – http://en.wikipedia.org/wiki/Waterfall_model ).
As part of this assignment you will be taking your screen designs in front of an end user group – and you will be taking a role as an end user. Users for this assignment take on 2 roles;
1. Users involved in the requirements of the project
2. New users
Members of the class will take on the role of New Users, your project clients will take on the role of users involved in the requirements. For each class of users you must;
1. Present designs of multiple functional screens of your project by having users actually use them,
2. Collect and document feedback from the users,
3. Develop an action plan on addressing the user feedback.
All this should be formally documented and that documentation will be the submission of this assignment.
Information
There are many plans and strategies towards collecting user feedback in software. One method is the observation meetings where you put the user in the driver seat, give them a task, and simply observe. Other methods involve the use of continuous feedback mechanisms where users can submit thoughts and feedback throughout the entire life cycle of the software.
For this project you should have a strategy for how to observe and collect user feedback. This is important to ensure the core functionality of the software is what the user expects and you have a quality product that meets the needs and expectations of the users. The best way to do this is live test where you observe an end user and collect data while observing. A close second is the allow users to “have a go” at the site and answer questions you may have on the interface.
Estimated Completion Time
You will be involved in this aspect of the project from both sides. You will be collecting feedback from others on your project and also providing feedback on other projects. Total amount of time on this task can be 10-15 hours as observer (to prepare, observe, and document), 2-3 hours as a user.
Supporting Lectures
None – but can easily make some if needed. This material is covered in CEN3722 Human Computer Interfaces – http://cen3722.pbworks.com/w/page/101283553/FrontPage
Questions and Answers
External Resources
There are plenty of resources, ranging from software tools to simple strategies for collecting user feedback. A Google search can provide a wealth of information here and is a good approach to tackling this. Also the bulletin board should be used to discuss strategies.
Grading Criteria
A submission and being listed as a tester will earn you a 10 – you should be well on your way to a fantastic project.