Skip to content

Retrospective

Jump to bottom
Kyle Cancio edited this page Apr 5, 2023 · 6 revisions

2023

Action Items

  • Bug reporting. There must be proper documentation of all bugs.
  • tbh we're Too dependent on lead
  • Deciding who gets to work on what file to avoid future merge conflicts.
  • ~~need to improve deployment workflow ~~
  • Test framework for slash commands
  • Fix Job Hiring Feature
  • Balance number feature tasks vs number of available QAs

Sprint 3

[2023S2] Progphil-Bot

Participants: pip, Pip, maw, CunningBard(Publiic Bard - Sir kyle), soumynona, draBgnninuC, Tora, Len, anonymous, maw, Anubis, Anon, guest, Jed, Allen, Set, dfasdf, Anonymous, Jed, Jed, Ya Void, Kyle

What Went Well

  • This sprint went well because of jed did most of the tasks. ( Anonymous )
  • Developing most of the tasks went well (most) ( Jed )
  • Good job to the team despite of busy schedules ( Anonymous )

What Didn't Go Well

  • I haven't contributed anything to this sprint because i became a busy human because of school ( Anonymous )
  • I think the number of tasks to be tested overwhelmed the number of available QAs ( Anonymous )
  • The job hiring feature was deployed but is not available due to scraping issues ( Anonymous )
  • I couldn't assign myself tasks since by the time i got free time(late march) the tasks were already assigned didn't wanna do work on an assigned task since merge issues is very likely ( guest )

Sprint 2

[2023S2] Progphil-Bot

Happy

  • Finished tasks on time
  • Were able to finish targets before end of sprint
  • no major problems encountered
  • most problems are fixable. devs are great!
  • Kudos to the devs for sprint 2 despite school stuff

Meh

  • need to improve deployment workflow
  • Want to add Logging but im in QA

Sad

  • Prod issue on Trivia Bot --- we dont talk about bruno
  • UI Development (not enough)
  • I havent done any contrib since moving to QA and it looks like there is no testing framework for slash commands in dpy

Sprint 1

[2023S1] Progphil-Bot

What Went Well

  • finished tasks on time
  • Creating the commands went smoothly though some merge conflicts happened but it didn't really get that much in the way
  • We fix bugs as soon as it gets reported :3
  • Jed's a good TL he's always responsive to my queries
  • We all can agree Jed went well

For Improvement

  • tbh we're Too dependent on lead
  • Deciding who gets to work on what file to avoid future merge conflicts.
  • Documentation. Documentation must cover all aspects of the project
  • Bug reporting. There must be proper documentation of all bugs.
  • Branching strategy I am still in doubt on trunk strategy may cause messy cherry-picks and releases.. Adding of automated testing
  • People please create the wiki. . a task was suppose to be done if not for the wiki
  • Discord Docker Image is too big. (150mb+) Idk if this fine but maybe could to compress it down more with alphine build i guess.
  • Team work and communications?

Continue Doing

  • Continue to use pipe server
  • Fixing bugs as soon as it gets reported
  • Research for more Features
Clone this wiki locally