Stating the Final Idea

In recent weeks we have had lots of discussion with our client on an effective solution to their proposed application project. We have partook in several negotiations ( Presentation 1 & Presentation 2 ) with the client discussing ideas, designs, audiences and concepts. There have give us feedback on several occasions (Feedback) of which we responded to in quick and effective manner. From this we set out expectations of the product/app in our MoSCoW to identify key features connected to our concepts and ideas

Our final idea is as follows

We will be creating an iPad application using an image of Magna carta as a navigation interface, this app allows the user to zoom into and explore the intricate details of the document. The document will have overlays on each clause with a tappable hotspot to let the user see more detail about the selected clause. The clauses will be filterable by category to allow the user to see the specific clauses which interest them.

We have decided as a group to progress with this application because we feel that it meets the clients requirements for the project and is slightly different to what other groups proposed as it’s more to fit a specific need/purposeful for the cathedral. Also,  taking on a less optimistic application means it can be developed and refined to a high professional standard.

Meeting the brief 

For 2015 BU’s RedBallon Agency has been commissioned to create a app for SalisburY. Cathedrals Magna Carta exhibition in 2015. The app has been conceived/proposed as a series of exploratory interactive and educational works that can be accessed while walking round Salisbury Cathedral

As discussed with the cathedral our application will be fulfilling the outlined  of providing an interactive document for tourists to use and explore the clauses within the document and take a better look at the document digital through the use of a super high res image that will allow extensive zoom capabilities. The app plans to provide an informative and interactive to take a look into a rigid document that is difficult for the majority of audience members to understand its importance but, particularly what it says and what this means.

How we have or/plan to meet learning Objectives 

  1. An ability to control and creatively exploit the associated hardware and software; –  Build an application that is intuitive and adds an aspect to audiences experience that non digital or the cathedral cannot provide
  2. Originality, creativity and professionalism in the interpretation of a live brief, production conception, pitching, management and realisation of interactive media artefacts; – Within our presentations we have remained professional, throughout our presentation of ideas and dialogue with them in regards to ideas using their feedback to fore most develop our idea to there satisfaction.
  3. The ability to work effectively as an individual as well as part of a production team; – Remaining professional at all times we aim to work effectively to produce an professional application that for fills the needs of the client furthermore improving the experience for audiences at the cathedral.
  4. The ability to evaluate work undertaken in a reflective manner with reference to appropriate debates and conventions. – Working together as a team where we will self evaluate and group evaluate our progress, work skills and products to push forward the project.
Advertisements

MoSCoW

MoSCoW is a technique for helping to understand priorities where a projects time has been fixed, understanding the relative importance of things is vital to making progress and keeping to deadlines. MoSCoW allows prioritisation to be applied to the required tasks and meet the requirements set out by the client. For the team instead of saying a problem is high or low importance and priorities MoSCoW has a specific uses like Must, Should, Could or Won’t.

  • Must Have
  • Should Have
  • Could Have
  • Won’t Have this time

Have that implies when the result that are produced it will meet these constraints and demands set out in this section. For the client it states what the product will consists of providing a way to determine whether a project has been a success or failure due to if the set out MoSCoW priorities have been met.

An example of this could be an apple and shows how an apple has to meet the demands of the client (consumer). This can be applied to any client who has requirements and demands to be met.

  • Must – be the fruit Apple
  • Should – Be Edible
  • Could – Be red
  • Won’t  – be a Banana

Group MoSCoW

In developing the idea with the clients we have been asked to outset a MoSCoW initially as a discussion between the group and clients. This will allow us to determine the expectations of the project. This will then give us the opportunity to justify if our project was a success depending on if we meet the demands of the outset MoSCoW.

Must: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.

  1. Must use the High resolution Magna Carta image within the application. Large zoomable image where users can see the small details in the document.
  2. Must have a translation of at least the key clauses from Latin into English.
  3. Must have specific details about the document such as explanations of abbreviations and crossings out.

Should: Represents a high–priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary.

  1. The application should be made and optimised for an iPad.
  2. We should make it to be displayed in the Cathedral chapter house as a digital installation.
  3. We should use default gestures that are recognised by everyone to zoom into Magna Carta image, swipe gestures to access different parts of the application.
  4. We should have a variety of description of the clauses for different age ranges.
  5. Some supporting media (image) for each clause.

Could: Describes a requirement, which is considered desirable but not necessary. This will be included if time and resources permit.

  1. We could make it so it can be used in an iPhone/Mobile but realistically it would be too small to look on a phone.
  2. We could make different translations of the document (Limited to what translations the cathedral already has)
  3. Could have a range of multimedia to support the clauses (video, audio)

Won’t: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future.

  1. We wont have the Magna Carta image as the centrepiece of the application with hotspots imbedded as clauses.

 What Next??

When the project progresses further and the MoSCoW will be updated if any of the factors change due to client impact. Project development could also impact the outlined MoSCoW. Prototyping and testing could force it to be changed. At the point where the client and group both feel the MoSCoW is achievable there will be no further changes made as this is the requirement that both are expecting to meet.

Dsdm.org, 2015. 10. MoSCoW Prioritisation | DSDM CONSORTiUM. [online] Available from: http://www.dsdm.org/content/10-moscow-prioritisation [Accessed 18 Mar. 2015].

Update: Updated Moscow

Presentation Discussion & Feedback

Presentation 00/03/15

Today’s presentation we presented to Saif (client at Cathedral) and Steph (client at RedBallon) our refined ideas for the Magna Carta application. From there previous feedback we were told to change some aspects that we had initially proposed to them as discussed in a previous post.

The presentation was a success as it gave us a chance formally speak to both of them and discuss issues they had and issues we had with there proposed ideas.

Discussion

Idea 1 (Magna Facts)

– (Saif) Liked the idea however, another grouped proposed a similar idea which also included a timeline of events surrounding the Magna Carta.

– (Steph) This was a feature they wanted in the app and had approved them to continue with that idea.

Idea 2 (Clause contextualisation & translation)

– (Saif) Really wanted this within the application because its a necessary  feature and would be helpful for more engaging visitors.

– (Saif) like the idea of using the zoomable Magna Carta image as it would allow users to see the small details within the image.

– (Group) suggested that it might be abit boring as its quite a simple concept and will be every text based even though there would be accompanying images/media for each clause

– (Steph) Could the zoomable image be used as a way to navigate to different clause ?

–  (Group) Its a possibility and we would have to look into if this was achievable. However a clear problem is the size of the device (mobile) would make it difficult to use. Would need to be on a larger screen like an iPad or installation screen.

–  (Steph – Saif) Would it be possible to instal iPads in the exhibition area near where the Magna Carta is ?

– (Saif) Yes that would be a great feature for visitors. Is it possible to build the application for an iPad ??

– (Group) Yes it would be possible but we would need to discuss how we would go about creating it for ipad screen size, creating an installation and previous issue of navigating via the image.

Feedback

After the discussion with Saif and Steph we were given written feedback:

  • Age range: young teens/ Adults
  • Quirky Facts – list of quirky facts to swipe through. Nice idea be we have covered this elsewhere
  • MC Extreme Close Up – Makes use of the high res image the cathedral has.
  • Combine the close up with the translation of key clauses into english – possible translation into different languages
  • use MC as interface – hot spots allow information to pop up and explain things like abbreviations and crossing outs.
  • Cathedral very keen on this idea
  • optimized for iPad and it could be on display in cathedral chapter house.
  • more serious app – useful for research tool.

Saifs Comments – I think we should this of this as something for an ipad in the chapter house. personally, I would like to see a strong visual link between Magna Carta as a document, and being able to understand it through your project. So try and use the image as the entry point.

The clause by clause translation will be interesting as people sometimes try to find where various clause are in the real thing.

Groups Opinion – Going forward from this we need to have a discussion with of how to proceed as this would be a slightly different pathway to the groups as we would be producing it for an iPad and not the same app as everyone else. Secondly we need to look into possible was that we could produce the application as there is some complex and advanced features which we would have to look into.

Initial Client Presentation

The aim of our first meeting was to come up with a couple initial app ideas to present to our tutors and the client. We came up with 2 (well 2.5) ideas to present and wrote brief descriptions for them.

IDEA 1: Magna Facts (and quiz)

Short, obscure and interesting facts about Magna Carta, its legacy and local ties to salisbury cathedral. It combines sentence long facts with a range of related multimedia to engage the user. After a few facts the user will be presented with a couple of related multiple choice questions about what they’ve just seen. This is to engage the user further requiring them to remember and recall details about Magna Carta to have a more lasting impact.

Demographic: 16-25

IDEA 2: Magna Translation
Provide Latin version of Magna Carta, translation into English (possibly other languages), and a short clause by clause commentary/ explanation to provide further detail and context. Intended to be short and easy to read with concise, jargon-free commentaries, possibly accompanied with multimedia to better illustrate ideas. Also a high-resolution image of Magna Carta for the user to zoom into and explore the physical details of the document.

Demographic: 16-25


Both of our ideas took an information based approach to the brief with one being a far more sensible option, and one which is essentially a game. I’ll go into a little more detail about how these respond to the brief, with information  from our presentation.

With regards to demographic, we chose our target audience to be people like us – Young adults, possibly students, possibly visiting in groups etc. When we visited the cathedral we were told that they get a lot of group visits from students around our age, so obviously theres a demand there. If we aim it at people like us, we know exactly what we’d expect from an app for the Magna Carta exhibition.

As we’re students we obviously love learning so information is what we’d want from an app. Also as we’re young and were born into the information age we want it to be easily accessible in bitesize chunks to go with our short attention spans and love for technology.

Idea 1 (Magna Facts) was inspired by ÜberFacts which is an app which is simply countless, random, sentence long facts which the user can swipe through. What I really like about this app is how simple and easy to use it is, as well as addictive. As the facts are so short you end up swiping through and reading lots, struggling to tear yourself away. Our adaptation of this would only include facts related to Magna Carta and possibly Salisbury Cathedral. These facts could be about global impacts of the document, about how it was made, or whats happened to it over the years for example. After a few facts, the user will be presented with a couple of multiple choice quiz questions about what they’ve just seen. The aim here is to further engage the user, to get them to remember and recall details about Magna Carta To hopefully have a more lasting impact.

To accompany this we wanted to add in supporting multimedia to balance out the text We wanted to branch out from just using photographs and present information in more interesting ways. Here are a few examples and how they could be used (more details about this will be included in a future post):

  • Visual anatomy can be used to label various parts of the cathedral’s architecture
  • Timelines can illustrate key events leading up to and after the signing of Magna Carta
  • Maps are a good visual aid to give geographical context to certain facts
  • A scale can be used for comparison for example the heights of English cathedral
  • Animation is a great method for illustrating a short story, such as the process of making parchment
  • Side-by-side comparisons to visually show differences, allowing the user to actively compare images of the cathedrals restoration for example.

Our second idea is a translation of Magna Carta with a clause by clause commentary providing further detail and context to even the most obscure clauses. This would be a largely information based app focused towards the same demographic. The commentary is intended to be concise and easy to read, aiming it at general audiences so anyone can understand it. This idea was inspired by a website which also offered a commentary for the clauses. I found when I was reading them, often they didn’t make much sense or it wasn’t really clear why they were even included in the document so I would be good to get some more background information about it and learn about Magna Carta that way.

To make it more engaging and visual, images could be added to accompany each clause, or possibly a high resolution image of Magna Carta that the user than zoom into and explore on their own accord.

A few initial designs for this idea were made, to demonstrate potential functionality of it.

The first one features a long list view which allows the user to scroll down and select a specific clause. From there they will be presented with 3 options to view in Latin, English or read the commentary and then can chose from there.

Screen Shot 2015-03-16 at 15.54.56

The second layout idea was inspired by the calendar view which presents the clauses as a grid rather than a list to save space and make it easier to navigate. From there the user will be presented with collapsible sections to read the different versions of the clauses.
Screen Shot 2015-03-16 at 15.54.49Obviously there are some limitations to this idea as currently there isn’t really much to differentiate between clauses other than a number in a list, and there is a LOT of text which can easily get overwhelming and boring which isn’t exactly what we want. But as we’re just presenting initial ideas future developments can wait until we receive some feedback on our ideas.

First Group Meeting

First Meeting preparation

Ok as we all know meeting in the media school foyer at 12 on Monday 23rd Feb (tomorrow). Quick bit of work or something to prepare for tomorrow

  1.  If everyone could look at the brief, the lecture notes and what we have been told so far by RedBallon and decided on what you think are the most important point or things that need to included in the app. E.g the target audience features they want or information they want us to include.
  2. Secondly do some research into what apps for exhibitions, museums or heritage sites currently offer.
  3. Lastly think about how we are going to work this project in terms of all working on the project at the same time and communicating. As rob suggested we might no want you use Facebook and use a more robust or industry form eg WIKI or a Git.
Session Notes

To Do…Market research

  • Any common things
  • good ideas you found
  • Things we need to look at
  • (Information / entertainment)
  • 3 key points from the brief/lecture/
    (Round the circle 3 sticky notes each)

Research

  • Fun, Interactive
  • Client wants to focus on local history
  • Not to much text but must have some
  • Engaging
  • Target people who are not engaged
  • Mixed Media
  • Focus on Magna Carta
  • Information abut legacy of document
  • Current Apps
    ◦ Target audiences is for older
    ◦ Mainly maps and virtual tours
    ◦ Hard to make app with little text and sound
    ◦ Mainly mixed media
    ◦ Many languages
    ◦ Boring

From this research we discussed ….and had common thoughts about

Discussion topics:

  • Focus on Magna Carta
  • Target Audience: -> Demographic of us 16 – 25
  • Not to much Text
  • Local & Legacy
  • Stories/Facts -> Link to legacy
  • Think About
    ◦ Quiz?
    ◦ Multimedia

We had some common ideas surrounding information facts, contextualising the Magna Carta and quiz apps. From the group research and discussion topics we produced 2 possible ideas

Ideas

  • Interesting Facts (similar to Uber facts small simple quick)
  • Progression from this facts that you answer questions on (Quiz to reinforce meaning of facts)
  • Translation and contextualising application of the Magna Carta clauses

How The Session Worked.

postit

 

What Next..??