12b, c & d
Feedback received & action taken (ii)
Test user-group feedback
I organised a peer review meeting with my Applied ICT colleagues. They are an interesting bunch and I find their 'fresh' and laid back approach to life very intriguing. They are very opinionated on a broad spectrum of subjects let alone the appearance of HCIs. They are most definitely well qualified to give their opinions in a 'user-focused' way on my product and any other software product for that matter.
I wanted to establish their views 'on the whole', with a corporate slant, attempting to foster the professional project management skills we have been learning in unit 8. So in the end I decided not to create a boring questionnaire, ask each of them to look at the latest prototype and answer the questions as fully as possible but I did something else. I used the electronic whiteboard to display my current working model and asked them to make comments with strong justification.
To my surprise some wanted to get 'hands-on' with the prototype themselves. Opinions started to come by the dozen. "Users should be able to navigate all of the sermon details, not just the first and most recent addition!" was an insightful comment bearing in mind the reviewer hadn't seen the functional specification. This meeting ended up being much more productive than just giving out the prototype and a questionnaire to everyone.
Analysis of feedback
My of my peer reviewers didn't think that version 2.0 had satisfied the requirements with 'finesse'. However, when I revealed to them the rest of my plans for the final solution such as: inbuilt FTP output to web server, a sequential search and full navigation features, some started to say that it was getting to complicated.
My own evaluation of version 2.0 - how well does it meet requirements?
Having now become even more familiar with XML in VBA, my XSLT knowledge being deepened with help from Jeni Tennison's book: “Beginning XSLT” I am looking forward to presenting the final solution to the client.
Action to be taken/improvements to be made/intelligence gained
- I must take account of the comprehensive feedback received from the client and the test users by making the GUI as easy to use allowing them to navigate intuitively as possible.
- A search and simple navigation system must be provided to enable users to navigate to, update and delete sermon data.
- The transformation and upload must all happen in one swift movement but also keep the user informed.
Click next to see my final solution...
« BACK | Back to top | NEXT »
