Week 4: Scrum Retrospective
- Julia
- May 29, 2019
- 2 min read
Today we had a scrum meeting with our scrum coach Yvens in order to reflect on the previous sprint (Sprint 2). As the scrum master, it was my task to take notes and to also document our results from the retrospective on the blog.
In the beginning, Yvens reintroduced us to the concept of the scrum retrospective, after which we began. Each of us received a few blue post-its for "what went well" and a few pink ones for "what could be improved". Without looking at each other's notes, everyone was asked to fill in what came into his/her mind for both categories.
What Went Well
In this category, a few aspects were named:
Good team spirit, the team gets along well. We are also going to do a teambuilding event at an escape room.
Everyone likes our concept "myENSCHEDE" and is motivated to realise it.
The team members have a few good characteristics: Everyone is helpful and understanding of each other, friendly and respectful. There is a good mix of different types of expertise on the team.
In the beginning of the project, we started off really quickly with finding a concept.
We also have made a few achievements that we are really proud of: We found a partner store, already built a prototype and already did hardware tests.
The team blog planning and writing has worked well so far, the organisation of our documents on the Drive is clear and good.
We are problem-solvers: We address problems fast.
What Could Be Improved
In some of my previous blog posts, I already hinted at some potential improvement points that I saw, and I was curious to learn what my team thought and which aspects they were going to mention.
As we discussed the improvement points together in the team, a few key aspects took shape, that were mentioned by various members of the team:
We are moving slowly. All the progress that we are so proud of stems from Sprint 1, but in Sprint 2, we fell behind schedule.
The division of the tasks is not equal among the team members - due to absence and an uneven distribution of needs for areas of expertise. The result is that some team members had a lot more work to do than others.
A few tasks have not been assigned to anyone - or to everyone, which does not make the responsibility much clearer - and nobody takes care of them. Some unfinished tasks have been dragged along for two sprints already.
We had a high absence rate in Sprint 2: Filling in for other people's tasks keeps team members from completing their own tasks.
Feedback among the team on each other's work should be clearer. If we don't manage to put our feedback into words, we could consult a teacher and get help this way.
The communication in the team could be better.
Actions to Be Taken
In the next sprint, we are going to address the problems of an unclear and uneven distribution of tasks. To achieve this, we will attribute values to all the tasks and check for each person how high his/her score is. Then if some people have lower values than others, they can take on some additional tasks.
Comments