DailyPost 1151
CLOSURE OF AN EVENT – INDIA POLICE HACKATHON 2019
As the curtains goes down and the razzmatazz is over, the event is remembered in pics and one odd video clipping. The event is over in heart and mind as soon as one leaves the event venue. The closure happens only in form left over thank yous, sending back stuff left behind and finally closing accounts and any left over peripherals. If you are lucky you will get proceedings of the event / conference. For sure you will find a small write up and pics in the company magazine and other advertisement type material.
While the meetings have action points and finally an action taken report, most of the big events have any only a promise to meet again. Hackathon necessarily has to take a different route of closure. There might be ample reasons to say that it would just be technical closure, the Human Resource connects and the results thereof nobody knows; projects, reports, articles, patents, it can be anything.
The genuine closure of the Hackathon is technical, complex and tedious but that is it is supposed to be. The management process document of closure has to be created. The codes have to aggregated in a digital repository in this case GitHub, access provided only to the owners. The whole process documentation from the first submission to the final result should find its place in digital archive. From the problem statements to the final ppt presentations should be made available for future.
The details of useful Human Resource has to compiled and send across where it can made use of. What is most important in the final closure is the review of the source codes of at least the winners / top 10, corrected of the technical anomalies and then make product development to happen. The resources of guiding this development might come from the Hackathon resources but it would need other add ons for which funding would be required. The launch of the final products could be the closure.
A SUCCESSFUL CLOSURE IS A SUCCESSFUL HACKATHON.