Differences

This shows you the differences between two versions of the page.

--- report:prm [2026/04/16 16:05] – [Fourth retrospective - 2026-04-01] team1
+++ report:prm [2026/04/16 16:24] (current) – [Fifth retrospective - 2026-04-16] team1
@@ Line 280: / Line 280: @@
 | 4  | Mar 26 – Apr 1  | Refining, refactoring, developing & testing | 0 | Finished | 45.16 % |
 | 5  | Apr 2 – Apr 8   | Refining, refactoring, developing & testing | 0 | Finished | 44.82 % |
-| 6  | Apr 9 – Apr 15  | Finishing the interim | 1 | In progress |  |
+| 6  | Apr 9 – Apr 15  | Finishing the interim | 1 | Finished | 96.78 % |
-| 7  | Apr 16 – Apr 22 | 3D modeling | 1 | To do |  |
+| 7  | Apr 16 – Apr 22 | 3D modeling and developing | 1 | In progress |  |
 | 8  | Apr 23 – Apr 29 | Finalizing the components & materials list | 1 | To do |  |
 | 9  | Apr 30 – May 6  | Refining the interim | 1 | To do |  |
@@ Line 318: / Line 318: @@
 Due to the holidays, both the sprint backlog and the global backlog have mostly remained the same. All of the team members were unavailable for the majority of the holidays.
+== Sprint 6: ==
+The global backlog
 ==== Sprint Outcomes ====
 === First sprint ===
@@ Line 335: / Line 339: @@
 === Fifth sprint ===
 Due to the holidays, most tasks were left unfinished. The team underestimated the amount of tasks and assigned many of them before starting the sprint. Because of this, less than half of the sprint's backlog had been completed. The team has learned to take external factors such as holidays into accordance when deciding the sprint's backlog.
+=== Sixth sprint ===
+Firstly, the team had an outstanding presentation in terms of preparation, information, enthusiasm and conviction. Secondly, 31 out of 32 tasks were completed. Thirdly, the team held a very progressive retrospective.
+The team has improved in several factors and has only one carry over task. However, the team had poor meeting etiquette on Sunday. This sprint has taught the team a lot about themselves as individuals and also as a whole.
 ==== Sprint Evaluations ====
 === First retrospective - 2026-03-05 ===
@@ Line 404: / Line 413: @@
     * /
-=== Fifth retrospective ===
+=== Fifth retrospective - 2026-04-09 ===
+There was no retrospective this sprint due to a similar sprint backlog and project backlog.
+=== Sixth retrospective - 2026-04-16 ===
+This week, the team had an interim presentation and they had to deliver an interim report. This presentation was an important moment of practice for the final product presentation and this moment was also a moment of feedback.
 What went well:
-  * We got feedback on a big presentation, and we improved in overall communication, language and confidence. We made a very good interim presentation and received minimal negative feedback on our report.
+  * The team improved in overall communication, language skills, team confidence and individual confidence. There was minimal negative feedback on the interim report.
 What didn’t go well:
-  * The behavior and energy in the pre-interim team meeting.
+  * The team held a meeting on Sunday to prepare for uploading the interim deliverables. There was no engagement from certain team members and the overall energy was very low. Secondly, certain team members were unprepared.
-What we should:
+What should the team:
   * Keep doing:
-    * Keep the same energy like in our presentation. We were driven, showed passion and we were all on the same wavelength.
+    * Keep the same energy like in the interim presentation. The team was driven, they showed passion and the members were all on the same wavelength.
   * Start doing:
     * /
@@ Line 419: / Line 433: @@
     * Come to a meeting unprepared.
+In general, the team is very satisfied with the end result and finished almost all the tasks of this sprint. The team can now focus on the next deliverables and development.
 ==== Summary ====