Meeting Minutes - SeanSpires/Project1-306-Team-Stonks GitHub Wiki

Work Breakdown Structure

• Used Planhammer to create WBS
• Created overall project plan
• Optimisation (Parallelisation) should come before Visualisation
• Should take WBS to drop-in clinic to confirm it is correct
• Ryan wanted Sean to put ‘Minutes’ in the WBS. Said it about 4 times
• Sean does not like to use Planhammer

Presentation

• Started on presentation
• Need photos for presentation
• Slide delegation:
  
  • Slides 1-4 (Intro): Sean
  • Slides 3-7 (Challenges): Mario
  • Slide 8 (WBS): Tyger
  • Slide 9 (Project Network): Josh
  • Slides 10 (Gantt Chart): Ryan
  • Slides 11-13 (Conclusion): Sean

1. Allocation
   • Tester
   • Algorithm (Backend):
     • I/O - Ryan and Tyger
     • Josh and Sean
   • Frontend:
     • Mario and Tyger
   • Wiki/Documentation:
     • Ryan
   • Optimisers:
     • Implements parallelisation
     • Pair
2. Tests
   • No TDD
   • Dedicated tester(s) to write test and test code
3. Code
   • Peer Programming for algorithm
   • Set up input/output before Ryan leaves
   • MVC
   • NEVER PUSH TO MASTER BRANCH
     • Implement on separate branch then merge to master
   • Backlog
     • Use GitHub
4. Due next week
   • Valid (Not optimal) schedule
   • Simple GUI

Absent: Ryan

1. Need to fill in pair programming log
   • Josh/ Sean
   • Tyger/ Ryan
2. New Roles
   • GUI
     • Tyger as driver, Mario on wiki
   • Improving Algorithm
     • Josh as driver
   • Wiki
   • Update Gannt chart
     • Ryan
3. Mario is leaving next weekend (24/25th)
4. Interview
   • Waterfall model
     • Still in implementation
     • We consider unit tests still part of the implementation phase because we don’t consider it fully implemented without assurance that it is functionally correct
       • Wrote tests after
     • Wiki is being done alongside implementation
     • This project is more suited for a waterfall model as the requirements don’t change
   • How did we use planning phase in implementation phase
     • Used our dependencies to figure out what we need
     • Followed Gannt chart time and resources
   • Project Management
     • Group came to conclusion
     • Mario on UI as that’s what he’s good at
     • Ryan needed to leave so put him on what could be finished first
     • GitHub Branches
       • Every new task in it’s own branch
       • Task is finished when you’re able to create a pull request with the approval of the team
   • Pair programming
     • Sean/Josh: Only in person
     • Tyger/Ryan: Mix of both in person and remotely
   • GUI Dependency
     • Temporal dependency
       • Can be done in the same time but one is implemented before the other
       • GUI was created before algorithm but was only able to be used after algorithm was finished

Meeting held online

Presentation

• Slides
  • Current Progress
  • Testing
  • Our Code
  • Design Patterns used
  • Challenges
  • Next steps