Ανάπτυξη διαδικτυακής εφαρμογής στη μεριά του εξυπηρετητή, συμβατής με desktop, mobile και tablet συσκευών, για τη διαχείριση αθλητικών δεδομένων αθλητών στίβου, με χρήση της μεθοδολογίας Scrum Agile για την ανάπτυξη λογισμικού
Implementation of a cross-device server-side web application for managing and analyzing personal performances for track and field, using Scrum Agile software development methodology

View/ Open
Subject
Διαδικτυακός προγραμματισμός ; ΑθλητισμόςAbstract
This thesis is about developing a web application that keeps statistics about track and field athletes. For the development, the nowadays popular software engineering methodology, agile, will be used, and more specifically scrum. Scrum promotes teamwork, so I will develop the application with another programmer. I will write the code on the server side, create and manage the schema of the database and handle the API. The other programmer will work on the front-end of the application. Agile will be used in every part of the development process - coding, decisions, feedback.
The development process will be described in parts, called sprints, according to scrum. Every sprint will be the description of a week’s work. The first part of the sprint will be the sprint planning, where the goals of the sprint will be set, and there will be a short description of the desired outcome that we should have by the end of the week. The second part is called stand up, which is a sum of all the daily stand ups. This is where I declare what I did each day, while working on the application. Usually some decisions that I took, along with the other programmer, are mentioned. Stand ups are also used in order to describe the difficulties that are faced. The third part of the sprints is the sprint review, where there is a report of what worked and what didn’t during the sprint. The outcome is presented and the plans of the next sprint may be revealed.
By using technologies which are not very familiar to us, developing an application from scratch, and getting feedback from users, we expect agile to be suitable for our case, making communication the main aspect that will help us release a full product.
After finishing the development of the application, it is proven that indeed agile greatly helped in the development process. The application got developed in time, all the developed features are useful for its users, and the quality of the service is very good. The small iterations that had a working application as the outcome, every time, helped us get feedback early on, and improve fast. Overall, the agile methodology proved to be appropriate for our case, and quite possibly, much more suitable than any plan-driven process.