Personal Evaluation – Project Management

In evaluating the project, the overall process of development from start to finish was organised, structured and always pre-planned. Our final outcome ‘Photo Book’ works efficiently and effectively with the incorporation of smooth interface interactions. These interactions include a varies of touch and swipe functions. Moreover, ‘Photo Book’ is seen to correspond extensively to the given brief, being designed as an element of an app and reflecting the graphics which have already been produced for the exhibition by RedBalloon.

With defining what was effective within the project, I believe that the communication infrastructure that was set up constituted to the collaboration and organisation of tasks which led to further idea development within the group. In addition, within the research and idea development stage I understand that we came up with a strong initial proposal and this derived a sufficient end product concept design. Personally, I consider that I myself was a firm team leader with the setting of individual tasks, organising group meetings and strongly within the idea generation stage. In my role, I was very much in charge of contacting the client, RedBalloon and raising group questions to the course lecturers. In addition, I myself set up the multiple contributor blog and the collaborative google drive which was used for the purposes of communication and assessment for the specific project brief. In relation to what wasn’t effective within the project, we had trouble initially in presenting our idea to the client and for them to fully understand the concept but by applying it to examples and giving graphic demonstrations this problem was resolved. Furthermore, with relation to my role I found it least effective when I wasn’t being critical in what was needed by each team member, so in tackling this problem I created a defined to do list for the blog posts which was uploaded onto the collaborative group as well as helping form an app content to do list in terms of the graphic designs.

In regards to future development opportunities, I propose to look into more customisable feature designs to expand the app further in terms of user interaction. With adding more customisable features such as different font styles it would allow the users to be creative and personalise their experiences to a greater level. Lastly, I propose to look into various different photo gallery layouts, to suggest further suitable structural designs, changing what is now a simple list design to an enhanced and structurally vivid feature.


Photo Book App Items

From the research gathered, I collated a list of 10 placeholder items for our Photo Book App. These were as follows:

1. Throwing down the Gauntlet
2. King John’s Taxes
3. Signing of the Visitors Book
4. The Magna Carta
5. Salisbury Cathedral
6. The Chapter House Frieze
7. The Prisoners of Conscience Window
8. Declaration of Human Rights
9. The Seal
10. Sword Play, Word Play

The placeholder items were chosen through the investigatory visit taken by Maria and Hayley and were collated through exploration of the research imagery. Each placeholder item is unique and corresponds to specific features within the Magna Carta Exhibition. In further production it was apparent for the placeholder items to include individual short informative summaries, in assembling this I emailed the client Seif El Rashidi and asked to be provided with descriptions for each placeholder. Continue reading Photo Book App Items

Group Blog – To Do List

With relevance to the group blog, I decided upon creating a group blog to do list. I created this to do list on Google Drive on an EXCEL spreadsheet. The to do list was established to ensure that every individual of the group understood exactly what they should be blogging, in addition to allowing for tracking of blog progress and assistance with colleague blog titles. Before Easter, I posted on the Facebook Group specific blogging requirements for the project, these were as follows:

When blogging ensure the following:

  • Each post should be around 500 words
  •  Ensure that your being critical when posting (more marks)
  •  Use tags & categories in your posts
  •  Use references where possible (more marks)

You should be blogging on your specific tasks you have done for the project as well as research. In constructing and fulfilling these requirements, I believe that the blog element of the project will be a success through strong correspondence to the brief and critical exposure. Below is a screenshot of the Google Drive Document for the Group blog to do list:

Screen Shot 2015-05-18 at 10.28.55

The to do list was constructed so that titles could be added to each individuals to do list section and when completed the team members can colour code each title blue to illuminate their blogging process. In doing so, it allows for each individual to understand their own progress and peer progress for purpose of our individual contribution evaluations.

Project Prioritisation Proposal

As a group, we were given a project prioritisation proposal document to fill out and complete. This documents purpose is to define the project deliverables for the given assignment, using the MoSCoW project prioritisation technique. Lawrence and myself filled in and completed this and then I myself forwarded the document on to our Course Director Simon Perkins.

Below is the filled in copy of our project prioritisation proposal:

Screen Shot 2015-05-18 at 09.18.48 Screen Shot 2015-05-18 at 09.18.52

Prior to completing this, I undertook key research on the MoSCoW method, to better understand its use, purpose and effectiveness.

What is the MoSCoW Method?

The MoSCoW method stands for Must, Could, Should & Would.

  • M – Must have this requirement to meet the business needs.
  • S – Should have this requirement if possible, but project success does not rely on it.
  • C – Could have this requirement if it does not affect anything else in the project.
  • W – Would like to have this requirement later, but it won’t be delivered this time.

The O’s in MoSCoW are added to make the acronym pronounceable, and are often left in lowercase to show they don’t stand for anything. MoSCoW as a prioritisation method is used to decide which requirements must be completed first and which must come later or will not be completed at all. The must requirements are non-negotiable and have to be delivered. Failure to deliver even one of the must requirements will likely mean the project has failed. The project team should aim to deliver as many of the should requirements as possible. Could and would requirements are ‘nice to have’ and do not affect the overall success of the project. Could requirements are the first to go if the project timeline or budget comes under pressure.

In relation to the proposed assignment, the set deliverables raised by our group will be utilised in the prioritisation of tasks for the project, allowing for efficiency and effective time management.


Haughey, D., 2014. MoSCoW Method. Project Smart. Available from: [Accessed 19 March 2015].

Photo Book Presentation

After evaluation of the feedback, we decided to take idea 1 forward as our key idea for presentation. The presentation was held today on the 12th March in a seminar lecturer, we pitched our idea to the client, RedBalloon and our lecturer Liam Birtles. In preparation for this we created both a Powerpoint presentation of the key idea and an information hand out. The hand out was given as an informative descriptive pitch for all parties to take away at the end of the presentation, to inform a better understanding of the key pitched ideas.

Below is the presentation we created in Powerpoint:

Screen Shot 2015-05-18 at 08.30.08 Screen Shot 2015-05-18 at 08.30.13 Screen Shot 2015-05-18 at 08.30.16 Screen Shot 2015-05-18 at 08.30.19 Screen Shot 2015-05-18 at 08.30.23 Screen Shot 2015-05-18 at 08.30.27

In creation of the presentation, we included a brief summary of the key idea and questions which we proposed to ask the audience and then answer. We wanted to ensure that the presentation was clear, concise and easy to understand and therefore chose a suitable font and quantity of white spacing. In addition, we included notes at the bottom of each page to help each individual fulfil the criteria when presenting. Again, I delegated each page to a member of the team so everyone knew where they were participating in the presentation.

Presentation – information hand out

The information hand out was produced in Microsoft Word by Lawrence and myself. In the hand out we included a brief elevator pitch of the key idea, a detailed description and an example scenario of the app in use. Below is this information hand out:

Photo Book

Elevator Pitch:

Photo Book helps you to efficiently document your experiences at the Magna Carta Exhibition. Resembling a sticker book, users augment an informative app but with their own photographs of their experience.


  • The app will present a list of short entries to the user.
    • The text content of these entries will correspond to the relevant information panels with each of the displays.
  • When an entry is selected, a new screen will display, and the rest of the information (if there is more) will be displayed next to a drawn outline of the display, as a placeholder for the photograph.
    • When the user selects this placeholder, they will be presented the option to take a photo or use one from their gallery (if they would prefer to fill it in at a later time).
    • This image is chosen by the user, and not verified by the app. We want to encourage users to make their photos personal and fun by including their family and friends, making the resulting images creative and unique.
    • If time allows, we will also implement a share function here, where users can tweet their images with a corresponding caption about the exhibition.

Example scenario:

Visitor comes across the “parchment making” element of the exhibition. Wanting to capture the moment of them making the parchment, they load the Photo Book app, and find the corresponding entry (it has the same wording as the information panel). Here they can select to take a photograph, and then the result is loaded into the app alongside the entry.

Later, when they want to look at the photograph, they can see it alongside the information that was at the exhibition, so they can relive the experience in a much richer way than by just looking at their phone’s built-in gallery.

Evaluation of the presentation

At the end of the presentation, we were given great feedback from the client, RedBalloon and our lecturer. They were happy about the proposed design and concept of the app and understood how it would fit within the Magna Carta Exhibition, therefore the presentation was very much a success. The next step is to start creating the structural app design and develop appropriate graphics for implementation.

Group Meeting 3

I arranged a group meeting for the 9th of March at 1pm in Weymouth House, Bournemouth University. The meeting was arranged to go over the two initial ideas for the project, in respondence to the feedback given from Stephanie (employee at RedBalloon). Below is the feedback given, which is in relation to our proposal pitch for both idea 1 and idea 2:

Idea 1 (feedback)

There will be an overarching structure/design that will look like a sticker book – where spaces are left for the user to insert their own images. Some text information and clues/shadow images as to what they are looking for will be provided. As the user walks around the Cathedral and MC exhibition they photograph what they think is the image they are looking for and insert it into the space in the sticker book.Target audience? Could we make it specifically for children who are more likely to engage with the sticker book idea? Presumably an image will be rejected if it’s the wrong one? We could have several sticker books for different ages or different themes – this would also encourage multiple trips to the Cathedral to complete the whole set. Assets – we need bespoke photography of images for viewers to find.

Idea 2 (feedback)

Simple questionnaire – how much have you enjoyed your visit , what would you change etc.. How can we make this more interesting/engaging?

Evaluation of the feedback

Within the meeting, we evaluated as a group the feedback from Stephanie. With reference to idea 1, firstly there is to be an overarching structure/design where spaces are left for users to insert their own images, however the idea is for the audience to replace rather an existing image to a photo which they have taken at the exhibition, thus creating an individual photographic experience. In addition our app element is to be marketed more for the general family use instead of children. Moreover, it is not possible for the app to allow for the rejection of images due to general production feasibility. Lastly with reference to idea 1 we will be looking at adding customisable options to its design.

Idea 2 was reformed to our original idea of the poll app, however as a group we feel this idea is not as strong as our first idea therefore we will not be progressing this concept forward. This is due to the fact that it was seen to be quite bland and also there is another group who is partaking on the design of a questionnaire stylised app.

Idea Pitch

All groups were given the task to outline in detail two conceptual ideas. These paragraphs outlines are summarised to include a short elevator pitch of the key idea, the target audience, its feasibility of production and how the app interacts within the given space. Lawrence, Shaun and myself wrote these descriptions collaboratively over a Skype call, all contributing to a document on Google Drive.

Before writing these descriptions we briefed ourselves on what exactly an elevator pitch is. An elevator is primarily defined as a short summary used to quickly and simply illustrate a profession, product, service organisation or event and its value proposition. It is widely credited by Llene Rosenzweig and Michael Caruso (Weller, 2011).

elevator-pitch (1) elevator #1

These paragraph outlines were then sent to our lecturer Liam Birtles who will consolidate these ideas further with Stephanie Farmer, a current employee at RedBallon.  Below is the following descriptions: 

Idea 1

Elevator Pitch: Stickerbook app which allows the user to create a fun, customised encyclopaedia during their visit to the exhibition, by using their own photographs to augment a set of listed items from the exhibition.

The first idea is to create an app which resembles a stickerbook, where the user has to collect photographs (as opposed to stickers) to complete it. The main concept is that audiences are given a part-completed encyclopaedia to fill out and develop whilst exploring the Magna Carta exhibition. Audiences are given information about particular objects within the exhibition and can then upload their own photographs of it to complete the template.

Users will be encouraged to be creative while taking their photographs, such as by posing in it, so that the app holds more personalised moments than a boring information leaflet.

Target audience: Suitable for all ages 15 and above, the app would hopefully appeal and be used by most attendees, due to the way that it contains useful and factual information about the exhibition. As far as production and programming goes, we are confident that this app is doable for the allotted time period. 

Idea 2

Elevator Pitch: Simple gesture based game. Player taps to make a character, in-game, take a selfie, and swipes to change poses, and gets points while taking selfies in the correct (as displayed on screen) pose.

The second idea is to create a touch-based game in which the player controls a character relevant to the Magna Carta (such as King John or the Barons), taking part in a selfie competition. This will involve swiping to achieve the correct pose, and then tapping to take as many selfies as possible. This app is not location specific, so could be enjoyed before, during, or after the exhibition.

Target audience: While the game is suitable and could appeal to all ages, the target demographic is ages 10 – late teens.

As far as production and programming goes, we are not as confident that this app is doable for the allotted time period.

Screen Shot 2015-05-11 at 15.06.42

In response to our email, we were told that feedback would be sent to us shortly. The received feedback will be reviewed by the team in a further group meeting.


Weller, M., 2011. The Digital Scholar: How Technology is Transforming Scholarly Practice.  Bloomsbury Academic: London.