Sprint 2 (March 21, 2023 - April 3, 2023)

[kbuffardi]

This thread is for conversations regarding roles, processes, and technologies we will use for Sprint 2 based on the retrospective held on the 21st.

[kbuffardi]

Some of my notes (in no particular order):

1. contributing.md has been updated with expectations for testing, feature branches, and accepting PRs
2. progress has been in the tech stack infrastructure, but this sprint needs to improve integration of the different technologies (e.g. postgreSQL database, github actions, reactjs, jest testing, Materialize UI, docker compose) so they are consistent and compatible
   • this integration will require a game plan to strategically integrate them, step-by-step. Input needed.
3. as we make progress replacing old code (e.g. mongo or EJS code) we need to remove dead code since even if we want it for reference, it is available in the git history (see release v0.1-alpha)
4. Some people have already committed code to main. That's great, but if you have done so, take a new role this sprint to help support others to make technical contributions such as navigating in pair programming, advising/troubleshooting, reviewing PRs, etc.
5. some incomplete issues are epic -- too large and should be decomposed into a bunch of smaller parts so smaller groups can make progress on reasonable-sized issues. For example, instead of broadly working on migrating to React, once the integration of the stack is prepared (2, above), individual features can be implemented in the front-end (e.g. user registration/authorization system) by smaller groups (or individual developers). Similarly, once that testing is fully integrated, it is the responsibility of everyone writing production code to also test it (with corresponding to policy in number 1, above)

And finally, my input:

• We can plan a Scrum of Scrums at the beginning of class at the end of each sprint, so we will plan one for April 4th. If it becomes a conflict with Design Pattern lesson class time, we will move future Scrum of Scrums onto the message board.
• We will perform future sprint Retrospectives within Discussion threads, like this one.
• As far as I can tell, the class is doing a good job managing the repo responsibly. I will let students take the lead on creating new Issues but if any questions arise regarding what the user needs/prefers, please tag me (@kbuffardi) in Discussion threads and/or Issues