Work Breakdown Structure - SeanSpires/Project1-306-Team-Stonks GitHub Wiki
Needs Work
During the planning phase, this Work Breakdown Structure (WBS) helped the team break the project down into different segments, each with their respective subtasks, outcomes, that need to be fulfilled.
The first segment is planning, which encompasses everything that needed to be done before the development of code for the project. This section includes the making of the project network, Gantt chart, WBS and also the research of the implementation and efficiency of algorithms suggested. Planning beforehand provides a general outline for the team to follow, reducing ambiguity when deciding the next steps to proceed with the project. Due to the importance of planning the project, this was given its own segment in the WBS.
The implementation of the algorithm is divided into four segments; the implementation, optimisation of the algorithm, creating the graphical user interface, and testing of our code. The implementation, optimisation and creating the GUI is to be done chronologically while the testing is done concurrently, ensuring that our code is functional and produces valid outputs in each iteration. The decision to split up implementation and optimisation was made because the coding process would be to make sure the implementation of the algorithm works, and only then will it be optimised. As one of the requirements was the visualisation of the algorithm, a GUI is needed. Each sub-task under this segment is an essential part of the GUI, as well as the interactive elements we have decided to implement.
While the first five segments of the WBS was in chronological order, the last two segments were overarching tasks that spanned the entirety of the project that our group believed would be beneficial. The Management segment contains tasks that coordinate how the project will be completed, which tasks will be assigned to which member. The documentation segment contains tasks that should be done throughout the entirety of the project, not just at certain points, such as the documentation of code, recording completed progress and meeting minutes. The writing of the report is also a sub-task under this segment.