Hackathon Time

Soon enough, in the blink of an eye, it was time for the Hackathon. Though I had already completed the database and implemented the classes, there was still an entire backlog of things that we have not completed individually and as a team.

During the Hackathon, we realised we had made two critical errors:

1) We had overestimated our personal abilities and our ability to meet the deadlines that we had set. We thought that we would be able to complete the tasks that we had set for ourselves every week. Coupled with the other tutorials that we had to do for other modules, we found that we had to constantly push back our deadlines, counteracting what the Sprint methodology is about.

2) As we were under the pressure to create something that would impress SAP, we set our sights too high, and set a scope that was not feasible to complete in time for the SAP demo. We severely underestimated the size of the project, as we looked at the project individually, we failed to realise how big and difficult the project would be when we tried to integrate all our individual components together.

With these two errors, it cumulated into many sleepless nights into the lead up to the Hackathon, where I still had to code the medical personnel side of the application. After struggling to pull through to create a demo, we finally created a demo, however even though the idea was a sound one, our demo was mostly hard coded and had little to no aesthetics in our front-end development.

This was definitely a lesson that I would remember in the future when doing projects.