During our Agile Methods course, we received a project that was done by last year's students. We have to plan 4 sprints, each lasting one week, and work on improving the project as part of the course. One of the things that we noticed first is that there are many half-baked things, such as event handlers missing for some UI events, bad coding habits / standards, messy code located in wrong places, and so on. The whole project is about 3000 lines of code, so it is not that complicated. The project is basically an app that processes PDFs, DOCXs, and TXTs for keywords, building a database of which keywords can be found in which files.
How would you guys approach such a task? Would you first try to refactor the whole code into a more readable state, thus spending a few days better understanding the code and building a better base for future modifications, or would you just continue adding new features and fixing bugs in the same style as the code itself?
Question
Guest
Hej hej,
During our Agile Methods course, we received a project that was done by last year's students. We have to plan 4 sprints, each lasting one week, and work on improving the project as part of the course. One of the things that we noticed first is that there are many half-baked things, such as event handlers missing for some UI events, bad coding habits / standards, messy code located in wrong places, and so on. The whole project is about 3000 lines of code, so it is not that complicated. The project is basically an app that processes PDFs, DOCXs, and TXTs for keywords, building a database of which keywords can be found in which files.
How would you guys approach such a task? Would you first try to refactor the whole code into a more readable state, thus spending a few days better understanding the code and building a better base for future modifications, or would you just continue adding new features and fixing bugs in the same style as the code itself?
Link to comment
Share on other sites
3 answers to this question
Recommended Posts