Synoptic units 8 & 10: Managing a multimedia project

Criteria

Project proposal (8a) &
The functional specification (10a)
(AO 2, 3)


Planning & monitoring (8b)
(AO 1, 2, 3)


The design (10b) &
Project management (8c)
(AO 1, 2, 3, 4)


Prototyping & testing (10b, c & d) &
Project management (8c)
(AO 1, 2, 3, 4)


Documentation & distribution (10c),
Project management (8c) &

The software product (8d)
(AO 1, 3)


Evaluation (8e & 10e)
(AO 4)

10b, c, d & 8c

Feedback received & action taken(ii)

My own evaluation of prototype

Fitness for purpose/audience

I am very pleased with the overall composition and theme of the product as a whole. I am convinced that choosing to model the website on the church's external notice board continues the church's image and forwards the purpose of product as well as appealing to a wide audience. It is contemporary yet neutral in the sense that it will not put off any from older generations.

The Flash invitation slideshow and the multi-lingual scripture box fits well into demographical context of the church's locality. Hounslow West is truly multicultural and the church's membership reflects this. We are all one in the Lord Jesus Christ and the website celebrates this fact very well.

Informal evaluative feedback from client

Below is a transcript of me getting feedback from the client via Skype.

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 board spectrum of subjects let alone website and multimedia production. They are most definitely well qualified to give their opinions on my product and any other multimedia product for that matter.

I wanted to establish their views 'on the whole/together', with a corporate slant, attempting to foster the professional project management skills we are learning in unit 8. So in the end I decided not to create a boring questionnaire, ask each of them to look at the 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 page by page ask 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. The horizontal sub-navigational turned out to be a complete failure in everyone's eyes! "It's too close to the main buttons at the top." "How are you going to fit all that you want to contain in the article and audio archive section in it? More than one horizontal list will make the top half look even more cramped," was a very insightful comment. This meeting ended up being much more productive than just giving out the prototype and a questionnaire to everyone.

Action required:

I must take account of the comprehensive feedback received from the client and the test users. The one thing that struck me the most was that both the main stakeholder (who is 30+) and my peer reviewers (who are all around the age of 18) both insisted that the home page was too crowded. "Only provide one sermon on the front page," ... "possibly too much information on one page," were all valid comments and I will incorporate this feedback when shaping, refining and completing the design and development of the product.

« BACK | Back to top | NEXT »