Teamwork

This last Friday, I was able to attend a Scrum meeting with stakeholders for the R&DC. The R&DC uses Scrum, an iterative and incremental agile software development framework for managing development. It defines “a flexible holistic product development strategy where a developmental team works as a unit to reach a common goal. In this case with R&DC, the project is the Repository | Images site. Those who attended were either the Scrum Master, team members and/or the scrum product owner. My supervisor, Nicole, is the product owner. She met with 4 other people to discuss their most recent two-week sprint. They discussed the interface of the Repository | Images site and also bugs that happen on the back end of it.

I realized how important it is to keep track of error messages and the wonky things that happen when working with MENU. It just goes to show that project planning is vital, especially when you get into the groove of inputting metadata and a bug makes you lose the work, those minutes add up and that in itself does not help with official deadlines.  I was only allowed sit in for the first part of the meeting. They also discussed and gave me a background on what they based their interface on. They also discussed the functionality and how they chose which collections to make public. I found it interesting that they were able to see how much progress they had made in their most recent two-week sprint via charts and graphs. One of the attendees of the meeting was a developer. I really love the amount of communication and productive teamwork between the three teams that make up the R&DC. It is very inspiring to see teams of people working together and making progress.