Jessica Spinetti Retrospective Sprint 1
Jessica Spinetti - Retrospective for Sprint 1
Links to Activity
-
I dove into researching the CI/CD community. In my findings, I referenced several helpful videos as well as a podcast and websites with tutorials of how to use Docker. Issue #36 (closed)
-
I created a folder to store the templates that will be used throughout the duration of the project. These templates include Spike and UserStory. Issue #43 (closed)
-
I updated End2End's README.md file in order to get a better understanding of the purpose of the End2End section of the project. Issue end2end#31 (closed)
-
I populated the Planning section of ViewOrder with the legal documents. This included licenses, authors, and Code of Conduct. Issue #31 (closed)
-
I edited and posted the team's Working Agreement in the Working Agreement portion of the Issue Board for ViewOrder. Issue #40 (closed)
-
I created a Meeting Time issue for the Working Agreement section for quick reference. This serves as a reminder and reference document for the team throughout the duration of the project. Issue #38 (closed)
What Worked Well
In my opinion, the team did a great job with open communication and time management. After the issues for the sprint were created, they were fairly divided up by weight among the team members. Each member of our team was responsible for certain tasks and completed that task (whether it be research or document construction) by the designated due dates. I believe our methods for communication (email, messaging, and zoom) are all extremely effective for a productive work environment.
What Did Not Work Well
For this sprint, I cannot pinpoint a specific thing that did not work well. We had a solid foundation in terms of communication since ViewOrder did not exist before this semester. Most of Sprint 1 comprised of research and the creation of folders or documents. I believe the team did a great job with this setup. Should there be any particular instances where something does not work well in regards to progress for the project, the team will handle that with communication and compromise.
Changes To Be Made For Team Growth
Currently, most of the issues addressed this sprint were handled on an individual basis. This means that it was nearly impossible to find conflict somewhere. Moving forward, if we encounter situations where multiple people are working on an issue or part of the project, it would be handled with clear communication and discussion to make sure there are no conflicts or misunderstandings.
Changes To Be Made For Individual Growth
In terms of personal growth, I believe I made some strides in regards to self organization through Gitlab. I was rusty on the operations of Gitlab but believe I relearned to basic structure. Moving forward, I will need to stay on top of deadlines to make sure I am able to upload all of my research/work for the project on time. I find that time is sometimes a blocker and will have to acknowledge the responsibilities of the sprint to itemize the tasks rather than try to take every issue assigned to me at the same time.