report:prm

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
report:prm [2026/04/08 17:05] – [3.4 Quality] team4report:prm [2026/04/16 15:26] (current) – [Sprint Evaluations] team4
Line 19: Line 19:
 Each main component is further broken down into smaller elements, representing the key functionalities required for the system to operate. This visual representation helps clarify the scope of the project by identifying all relevant parts of the system and their relationships. Each main component is further broken down into smaller elements, representing the key functionalities required for the system to operate. This visual representation helps clarify the scope of the project by identifying all relevant parts of the system and their relationships.
    
-(See Figure {{ref>fig:Product}} for the wbs for the project and see Figure {{ref>fig:Management}} for the wbs of the project).+Figure {{ref>fig:Product}} presents the WBS for the product and Figure {{ref>fig:Management}} the WBS of the project.
  
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:Product> <figure fig:Product>
 {{ :report:wbs_product.png?nolink&600 |}} {{ :report:wbs_product.png?nolink&600 |}}
-<caption> Start of a WBS </caption>+<caption> WBS of the product</caption>
 </figure> </figure>
 </WRAP> </WRAP>
Line 31: Line 31:
 <figure fig:Management> <figure fig:Management>
 {{ :report:wbs_project.png?nolink&600 |}} {{ :report:wbs_project.png?nolink&600 |}}
-<caption> Start of a WBS </caption>+<caption>WBS of the project</caption>
 </figure> </figure>
 </WRAP> </WRAP>
Line 43: Line 43:
 <table tab_labelmilestones> <table tab_labelmilestones>
  
 +<caption> Milestones for the project </caption>
 |< 100% 90px >| |< 100% 90px >|
 ^  Date  ^ Description ^ ^  Date  ^ Description ^
Line 67: Line 68:
 |  :::         | Bring **typical food** from your country | |  :::         | Bring **typical food** from your country |
  
-<caption> Milestones for the project </caption> 
 </table> </table>
 ==== 3.3 Cost ==== ==== 3.3 Cost ====
Line 117: Line 117:
  
 <table tab_label6> <table tab_label6>
 +<caption> Table of different risks </caption>
 ^ Risk ^ Description ^ Probability ^ Impact ^ Risk Level ^ Mitigation Strategy ^ ^ Risk ^ Description ^ Probability ^ Impact ^ Risk Level ^ Mitigation Strategy ^
 | Technical failure (sensors/electronics) | Failure in integration of sensors, electronics, and structure in marine conditions | Medium | High | High | Test components and validate system | | Technical failure (sensors/electronics) | Failure in integration of sensors, electronics, and structure in marine conditions | Medium | High | High | Test components and validate system |
Line 130: Line 131:
 | Waterproofing failure (IP68 breach) | Water entering electronic components causing malfunction | Low | High | Medium | Seal testing and proper enclosure | | Waterproofing failure (IP68 breach) | Water entering electronic components causing malfunction | Low | High | Medium | Seal testing and proper enclosure |
 | Data transmission failure | Loss or interruption of data communication | Medium | Medium | Medium | Local data storage and redundancy | | Data transmission failure | Loss or interruption of data communication | Medium | Medium | Medium | Local data storage and redundancy |
-<caption> Tabel of different risks </caption> 
 </table> </table>
  
Line 338: Line 338:
 **Summary** **Summary**
 Overall, the team made good progress in design, organization, and collaboration. However, some uncertainties and planning issues remain, and the team needs to focus on clearer decisions and more structured work moving forward. Overall, the team made good progress in design, organization, and collaboration. However, some uncertainties and planning issues remain, and the team needs to focus on clearer decisions and more structured work moving forward.
 +
 +**Fourth week retrospective**
 +
 +**What went good**
 +The presentations went good, and the components were selected.
 +
 +**What went bad**
 +The communication presentation did not go that well
 +
 +**Ideas**
 +No ideas
 +
 +**Actions**
 +For the next week, the team need to finish the interim report, and deliver it.
 +
 +**Fifth week retrospective**
 +
 +**What went good**
 +The interim report was delivered
 +
 +**What went bad**
 +Should have done the report finish before the sunday.
 +
 +**Ideas**
 +No ideas
 +
 +**Actions**
 +For the next week, the team are prepering for the interim presentation.
 +
 +**Sixth week retrospective**
 +
 +**What went good**
 +The prep for the presentation
 +
 +**What went bad**
 +...
 +
 +**Ideas**
 +Some of the feedback from the supervisors were to have fish in the flyer/brand. The team will look in to it.
 +
 +**Actions**
 +For nexts week, the team are going to research more of the smart box, to check if there are different batteries to use and how to design it in the best way. Also to create a 3D-model video of the product.
 ==== Summary ==== ==== Summary ====
 The project has been managed using an iterative and structured approach, allowing the team to balance technical challenges with continuous development. Through defined scope, milestone planning, and Agile methods, the team has made steady progress in both design and implementation. While some challenges remain, particularly related to decision-making and organization, the project is moving forward with a clearer direction and improved collaboration. The project has been managed using an iterative and structured approach, allowing the team to balance technical challenges with continuous development. Through defined scope, milestone planning, and Agile methods, the team has made steady progress in both design and implementation. While some challenges remain, particularly related to decision-making and organization, the project is moving forward with a clearer direction and improved collaboration.
  • report/prm.1775664302.txt.gz
  • Last modified: 2026/04/08 17:05
  • by team4