8e & 10e
Evaluation
Of the final outcome
The extent it meets the specified requirements - was it a success?
In my final overall assessment and analysis of the product that this entire project has evolved around, I have concluded that it was successful in meeting the vast majority of the requirements. I believe I can give many reasons for this. However, the main reason is clearly evident which is that I had good dialogue with the main stakeholders. Mr G Yuen has recently commented in an email: “Those who've seen the new site say it looks very good!”
The end of project review meetings findings will shed light on this whole matter:
- 5. Key success criteria analysis:
“The website must achieve all five objectives listed in this document.”
· The product achieved four out of five of these objectives.
“No extra cost will be incurred by HWEC.”
· This criterion was met - the treasurer wasn't even aware of the revamp!
“Users will be able to download sermons easily and efficiently.”
· Mr G Yuen, Rev R Hollands and Mr D Hollands all agreed that this was true of the final product and pod-casting aided this.
“The product is accompanied by all the deliverables.”
· This was true.
“The project is completed ready and ready for handover before: 30/04/07”
· The deadline was met.
However, I failed to meet one of the clear and quantifiable objective which I optimistically defined in the functional specification many weeks ago.
Short comings explained...
For the last couple of days I have been reflecting on why I didn't achieve the goal:
- “Users will be provided with a choice of 3 display options on the ‘Accessibility’ page, which are: No style sheet, default style and high- contrast style (this will be done using client-side scripting).”
The biggest contributor to this failure was that I lost sight of that particular objective early on, I should have referred back to the functional specification in a more rigorous manner during the early prototyping stages. I only remembered defining that requirement, when I finally got round to building the 'accessibly' page. This task happened near the end of the prototyping process and sadly, I didn't have enough time to complete it. I did attempt it but because it involved editing some JavaScript, it was very tedious for an inexperienced programmer like me and it started to take up too much time so I decided I had to stop. Mr G Yuen said in the end of project review that he would look into it in his spare time.
The effectiveness of the solution
It is my belief that the product didn't just simply meet the requirements but actually went beyond them in an effective manner. If the single short coming is forgotten, the product produced is attractive, engaging, interactive and exciting. The sermon audio is good quality also - hopefully this new, church-based outreach will prove useful and have a transforming effect on someone.
How it could be enhanced in future
The minister's wife, Ruth, has suggested that it would be really good if we could make contacting the church easier. At the moment, we provide the church's postal address, the manse's phone number and the enquires email address. Together, with her, I have envisaged an engaging way of contacting us: by asking them to give feedback about the audio sermons via forms. These could then be used to make the most of the multimedia available on site by making listening to the recommended sermons more desirable. At any rate, a contact form on the contact page would most definitely be well-thought out enhancement.
Another future in improvement could be create a multimedia blog for the pastor. He could produce audio posts, or even video posts and integrate them into a special place on the site.
Of my project management skills
Effectiveness of methods used
The interim review meetings went well and were well documented. The informal communications were the most insightful. Mr G Yuen has commented: “I was pleased that I have been able to track the entire progress of the project and I formally acknowledge the validity of the informal input that was carried out on Skype. This method of feedback appeared, from my view of the project, very effective.”
The task identification and time allocation was helpful and realistic. I was able to work out approximately how long it would take me from the very start of the project. This was the driving force behind the whole project, the silent helper.
Key lessons learnt
Plan early, keep to task. Review progress regularly. Ask people to ask you tuff, challenging questions about the project's current status. Build lee-ways in the original plan. Use the necessary contingencies as soon as you go behind schedule. Taking responsibility is daunting but necessary to be successful. Being well-organised is a must. Be accountable to someone close. Discuss progress regularly in groups. Accept critics views humbly. Learn from mistakes.
Justification of actions taken
The first project management decision I had to make was how was I going to deliver the product on time. I thought about the idea of building extremely detailed designs and one single prototype to gain the client's confidence but then I was introduced to the evolutionary-delivery model. This enabled me as a manager to understand that I didn't just have to waste time creating prototypes that wouldn't be apart of the final solution but that I could build on each prototype layer after layer, consulting the main stakeholder as I went along.
I felt it necessary to do it this way. Mr G Yuen, in the first formal meeting, didn't understand why I needed to take this prototyping delivery route, he thought that the prototypes would be a waste of time for smallish product like mine. However, I managed to persuade him of the benefits of more specific feedback and testing that would accompany each build and he eventually came round. Without this decision, I don't think the product would be as successful.
Of my current multimedia skill level
I believe I am a very competent user of Adobe Fireworks and Adobe Dreamweaver, but I do have a lot to learn about Adobe Flash.
I found using XML in Flash for useful purposes fascinating. I continued to research and read and have learnt a number of new techniques. I purchased a very helpful book called: “The Flash Anthology: Cool Effects and Practical ActionScript” by Steven Grosvenor. It provided me with helpful insights into the practical application of Flash's ActionScript and was the inspiration behind the XML slideshow.
Using the Creative Labs Audio recording and editing software was a breeze. I feel very confident capturing sound in future.
Areas for improvement
Adobe Flash and the use of JavaScript and ActionScript in dynamic multimedia design.
Of my own performance
Comments on Mr D Hollands’ performance from the end of project review:
- “Mr G Yuen said that he has been very impressed with the way Mr D Hollands has conducted himself in a professional manner. However, he was concerned that Mr D Hollands did not involve his senior management much, only a very little. Mr D Hollands replied with the justification that he did not want to be ‘hand-held’ by senior management but wanted to work independently. He did then go on to admit that he should have provided more regular reports to senior management.”
- “Rev R Hollands admitted that the absence of contact with the more experienced senior management did concern him too; however, he could see the difficulties of organising, for example, a meeting with Mr Yuen, himself, Mr D Hollands and Mr A Atar being arranged. Overall it was agreed that the project was successful despite not accomplishing one of the objectives. Further evaluation would suggest that it shouldn't have been an objective in the first place.”
The above comments speak for themselves. However, I would to say, that I do take their point about my lack of involving senior management. Overall, I should have been more pro-active in my communications with him.
Strengths as a project manager
Planning - I find it easy to draw up plans but sticking to them is a harder task. However, in this unit I have been able to work to plan well. I can't say that about many of my previous units!
Communication with client - maybe I was at an advantage because I already knew the main stakeholder Mr G Yuen fairly well. Notwithstanding that, I believe I have been able to handle the formal communication very effectively.
Weaknesses as a project manager
Communication with senior management - this was different. I was so keen to not be given extra support that I shyed away from involving Mr A Atar much. I wanted to stand on my own two feet in the project management world.
Areas for improvement
Reporting progress to senior management on a regular basis and not going beyond the project definition outlined in the specification.
Overall
Personally, I have enjoyed rounding off this GCE in Applied ICT with managing a multimedia project. It has enabled me to be creative and develop valuable presentational skills - conveying information in an effective and engaging way. It has also given me the opportunity to benefit my local church in a number of ways. The project management skills and methods gained here, will also be of future use at university and in the workplace.
