In this section I will justify my choice of choosing agile over waterfall and talk about other common techniques found in agile environment, that I have applied. I decided to include this chapter because I believe the way you approach development strongly links to the final outcome.
The nature of my project involves making many changes as I am producing the application. Therefore, I decided to choose agile development for this application. This means I am not doing any heavy documentation and my design stage does not have to look like the final product. This is because I have limited time and all of the heavy documenting is not needed since I am working alone. This gives me greater flexibility in making any changes for example changing the requirements etc. If I have chosen waterfall development, I couldn’t flexibly switch between different development stages. Doing waterfall was impossible in my case because I couldn’t design diagrams that would look like the final product due to the fact that during this project I was learning many new skills which I wasn’t sure would work as planned in design stage. …show more content…
I used Kanban to insure there is a steady flow of tasks. Kanban is a type of time management system developed in Japan for the computing industry. So I would split my table into 4 categories: backlog, in progress, testing, completed. There is a wip limit on 3 of those categories so that you have to finish some of the tasks before starting working on new tasks for example in progress has wip limit of 2 this suggests I cannot work on more then 2 tasks at a time. This wip limit helps work flowing and save time by eliminating task switching. For this approach I have used board in my room and I used stick notes to represent different processes. I believe this philosophy helped me to save valuable time and replaced the gantt chart which was initially
The nature of my project involves making many changes as I am producing the application. Therefore, I decided to choose agile development for this application. This means I am not doing any heavy documentation and my design stage does not have to look like the final product. This is because I have limited time and all of the heavy documenting is not needed since I am working alone. This gives me greater flexibility in making any changes for example changing the requirements etc. If I have chosen waterfall development, I couldn’t flexibly switch between different development stages. Doing waterfall was impossible in my case because I couldn’t design diagrams that would look like the final product due to the fact that during this project I was learning many new skills which I wasn’t sure would work as planned in design stage. …show more content…
I used Kanban to insure there is a steady flow of tasks. Kanban is a type of time management system developed in Japan for the computing industry. So I would split my table into 4 categories: backlog, in progress, testing, completed. There is a wip limit on 3 of those categories so that you have to finish some of the tasks before starting working on new tasks for example in progress has wip limit of 2 this suggests I cannot work on more then 2 tasks at a time. This wip limit helps work flowing and save time by eliminating task switching. For this approach I have used board in my room and I used stick notes to represent different processes. I believe this philosophy helped me to save valuable time and replaced the gantt chart which was initially