DMU logo

Call For Proposals

Call for Proposals for Hackathon 2017

We are looking for proposals for developing applications to help with problems in health, assisted living, social care and communities. This application could be in the form of a mobile app, a web application (an application which runs in your browser), stand-alone applications or games. Submissions from local councils, hospitals, charities and local businesses are some of the examples of submissions from previous years. Our aim is to use expertise within universities to help public services, charities and small businesses  to find solutions for their problems where there may not be enough funding to solve the problem through normal channels. The solution should have an impact on vulnerable people's lives and the problem should benefit from collective wisdom of experts working together.

Here are some notes to help you with writing and submission of your proposal. 

Basic idea and design

If you have an idea for an application for the Hackathon event, please read the following instructions to ensure that the idea is new and requirements and functionalities of the application are recorded.

 

Step1: Please check to see if a solution already exists, search app stores with a wide range of keywords. If a solution does not exist or if it exists but does not have the features you need, then it is worth going forward and innovating the product.

Step 2: Understand your audience:  Who are the people that will use your app? And is it really wanted/required? A tip is to ask 5 people who make up your audience and to ask them if they would use the application and if so what kind of functionality/features would they like within the app?  It may also be worth getting those 5 people to become your user focus group after the Hackathon. Spending time with your audience to test your work will produce dividends. They can see if it works and gives you constant feedback on improvements.

Step3: Write down details of the application's usage, functionalities and specifications. The easiest way is to think about how the app will look, how it will flow from one page to another as well as its functionalities. Get this down on paper in some shape or form, with the end result being you have some idea of flow, the amount of pages you need and what each page has on it. This doesn’t have to be perfect; it is the transplanting of the idea from mind to paper which is the aim. 

Step 4: Working in isolation on any project will deny you the pleasure of other people's company, the sharing of tasks and the input of ideas and experience from others. Experience shows that the best way to turn up to a Hackathon is with a team of people from your organisation or social network, each willing to put in some work into the process, sharing a common vision. To this end, it is not recommended that this project is done in isolation. Instead, share your idea to be submitted with people you know and look to develop a team of 2 or 3 people before attending the hackathon.  Remember that it won’t be just during the Hackathon whereby support is needed, a commitment to meet and work on the idea with the team from the hackathon will more than likely be needed for some time after the event, if you want to make the application a reality. Important Note: if your application is going to work within your organisation you need to bring along the technical person who could provide necessary information for integration and can access to test and install the software on a test platform.  Please also mention this in your submitted proposal, as otherwise all the work might be lost if you are left with a piece of software to install on a complex system on your own after the event. 

Step 5: Sustainability after the Hackathon: the hackathon will more than likely not produce a final application, but will start the coding process to a good level. There will be more work needed in the teams assembled after the event. This means more meetings, communication and work after the event. This is something to consider and be aware of before submitting an idea. Consider funding options for completing the application after the event. Finding funding sources based on the prototype created during the Hackathon is necessary to ensure the application will be completed and will reach its target end-user. This year colleagues from DMU's Research, Business and Innovation will talk to teams to find funding opportunities to continue the project after the hackathon, where possible. There are several sources of help in Leicester and we will introduce some of them during the event. 

Pre-Event Judging

The organising committee of Hackathon 2016 will cross-review all the applications and score them. Criteria for scoring are explained below. Please note that not all of the ideas and problems submitted to the Hackathon will be viable for the event. This could be due to a number of reasons including:

  • There are normally more problems submitted than can be solved over the weekend. The resources and people needed may just not be sufficient to work on all problems in a two days period.
  • Many of the problems submitted may already have a solution in the marketplace.
  • The problem may be too ambitious to achieve any of its objectives over the weekend.
  • The problems may not have demonstrated how they can or should work on paper sufficiently.

 

Selection Criteria

The ideas and problems submitted will be judged on the following criteria:

  1. Quality of the proposal: 25%
    1. Has any research into the idea been done? 
    2. How complete is the idea? 
  2. Impact: 25%
    1. Does it solve a problem that exists?
    2. What is the potential market? How many people could it potentially assist?
    3. Is it in line with the Hackathons objectives of trying to create supportive solutions to help communities and individuals?
  3. Innovation: 25%
    1. Is this a new solution to the problem? Does a similar product exist? Does it have any unique features to distinguish it?
    2. Does it innovate on any design features or technical solutions/aspects?
    3. Is there a new approach to an old solution (within the product) that already exists?
  4. Sustainability: 25%
    1. Is there a long-term vision for the idea and product?
    2. Is there a team behind this idea?
    3. How will this drive forwards after the event, until completion?
    4. Is there a possibility for funding for remaining of the project? Has this been identified and clearly described?

How do I submit my proposal for Hackathon 2017?

Ideas will be submitted via the link below. Submissions for Hackathon February 2017 are currently not open.

Submit your proposal

 
Technology Degree Show
Technology Degree Show

The Technology Degree Show highlights the work and achievements of our final year students.

DMU research news target area image
DMU research news

Read about our latest research efforts.