Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| report [2022/06/19 23:05] – [3.9 Stakeholders Management] team2 | report [2022/06/28 10:49] (current) – [7.7 Tests and Results] team2 | ||
|---|---|---|---|
| Line 53: | Line 53: | ||
| | Carla Gomes Cardani| Brazil | Design | Graphic Design and Marketing | | | Carla Gomes Cardani| Brazil | Design | Graphic Design and Marketing | | ||
| | Carmen Couzyn| Austria | Media Technology | Software Development | | | Carmen Couzyn| Austria | Media Technology | Software Development | | ||
| - | | Eliott Degouilles| France | Mechanical Engineering | Hardware | + | | Eliott Degouilles| France | Mechanical Engineering | Structure |
| | Julia Aleksandra Engst| Germany | Management (Building Real Estate Infrastructure) | Project Management | | | Julia Aleksandra Engst| Germany | Management (Building Real Estate Infrastructure) | Project Management | | ||
| | Jan Michael Benner| Germany | Energy Engineering | Quality Manager and Reporting | | | Jan Michael Benner| Germany | Energy Engineering | Quality Manager and Reporting | | ||
| Line 523: | Line 523: | ||
| ==== - Risk ==== | ==== - Risk ==== | ||
| - | The biggest challenge | + | Risks in general are understood as the danger that the realized result deviates from the planned result. This happens mainly due to unknowable events. |
| - | With a well-developed | + | |
| - | In the following our group identified key risk regarding to our product and our project: | ||
| - | ==== 3.7.1 Product Level ==== | + | There are four phases in the risk management process: Risk identification, |
| - | <WRAP center centeralign 750px> | + | ** Risk identification** - Collection of potential risks in various fields of observation that arise in the course |
| - | <table tlabel6> | + | |
| - | < | + | ** Risk assessment** - Evaluation of risks, depends on the risk preference of the decision maker. As a risk-neutral company, our decisions are based primarily on expected values. |
| - | ^ Risk Event ^ Probability ^ Impact Rating ^ Risk Handling ^ | + | |
| - | | technical issues (failure | + | |
| - | | delivery delay | possible | significant | guaranteed delivery on time | | + | **Risk management** - Development of strategies |
| - | | too costly | possible | moderate | make or buy decision, finding | + | |
| - | | public has hurdles | + | **Risk monitoring** - Review |
| - | </ | + | The individual processes do not represent completed procedures, but must be monitored regularly and re-evaluated when new information about a risk is available. |
| - | </ | + | The following tables are identified risks regarding to the project and product. |
| - | ==== 3.7.2 Project Level ==== | ||
| <WRAP center centeralign 750px> | <WRAP center centeralign 750px> | ||
| <table tlabel7> | <table tlabel7> | ||
| Line 552: | Line 549: | ||
| </ | </ | ||
| - | <WRAP centeralign> | + | < |
| - | <figure figlabel13> | + | <table tlabel6> |
| - | {{ : | + | < |
| - | < | + | ^ Risk Event ^ Probability ^ Impact Rating ^ Risk Handling ^ |
| - | </figure> | + | | technical issues (failure of parts) | unlikely | severe | creating stress simulation | |
| + | | delivery delay | possible | significant | guaranteed delivery on time | | ||
| + | | too costly | possible | moderate | make or buy decision, finding a cheaper alternative, | ||
| + | | public has hurdles to participate| unlikely | severe | strong study of the state of the art | | ||
| + | </table> | ||
| </ | </ | ||
| + | |||
| + | |||
| + | The biggest challenge of a project is that due to existing risks a project’s success can be achieved completely, partially or not at all. | ||
| + | With a well-developed risk management, the chance of achieving the project goal is increased and risks can be minimised through early and effective identification. Furthermore, | ||
| Line 571: | Line 576: | ||
| Users are the most important ones, especialy for our project where our first goal is to get them invested as much as possible. However, interaction with users will only be done though the use of parcitypate. Therefore, the product is completely designed to improve the participation rate and user experience. This is archieved through everything possible like the website but also via the design of the structure.\\ | Users are the most important ones, especialy for our project where our first goal is to get them invested as much as possible. However, interaction with users will only be done though the use of parcitypate. Therefore, the product is completely designed to improve the participation rate and user experience. This is archieved through everything possible like the website but also via the design of the structure.\\ | ||
| Clients are another very important stakeholder for any project. For parcitypate, | Clients are another very important stakeholder for any project. For parcitypate, | ||
| - | The last external stakeholders identified are suppliers. Their importance is great because the manufacturing of the product relie almost them. From the raw materials, to the shaping of parts, | + | The last external stakeholders identified are the suppliers. Their importance is great because the manufacturing of the product relie almost them. From the raw materials, to the shaping of parts, |
| ==== - Sprint Outcomes ==== | ==== - Sprint Outcomes ==== | ||
| - | //To be added. Include | + | The following tables show the weekly sprints, indicating |
| <WRAP center centeralign 750px> | <WRAP center centeralign 750px> | ||
| Line 779: | Line 784: | ||
| ==== - Sprint Evaluations ==== | ==== - Sprint Evaluations ==== | ||
| - | //To be added. Include | + | Due to the high workload caused by the lectures in the middle third of the project semester and illnesses |
| + | There is potential for improvement above all in a more balanced distribution of workload over the entire course of the project. The joint focus on finding a solution in the event of time bottlenecks should be emphasized positively. | ||
| ==== - Conclusion ==== | ==== - Conclusion ==== | ||
| - | //To be added. Provide here the conclusions | + | Well-structured project management serves as a key element to ensure a high-quality project that is completed on time and within budget. It is important to live project management throughout |
| + | |||
| + | In the following | ||
| ===== - Marketing ===== | ===== - Marketing ===== | ||
| Line 1374: | Line 1381: | ||
| </ | </ | ||
| </ | </ | ||
| + | |||
| + | In order to be able to transport the product to the later installation site, a packaging system was designed (see figure {{ref> | ||
| + | The concept produces as little waste as possible, so the product itself is used as a transport package and fixed with Vime. A bench, which is also used as packaging, can provide additional value. | ||
| + | |||
| + | < | ||
| + | < | ||
| + | {{ : | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | |||
| === - Selection of materials === | === - Selection of materials === | ||
| While designing the structure, we also had to decide which materials we want to use for each part. As explained in the sustainability chapter, we applied ourself several constraints about the materials selection : single material parts, material 100 % recyclable only, etc. Some other constraints come from the context and the use of the product : resist UV, rain, temperature, | While designing the structure, we also had to decide which materials we want to use for each part. As explained in the sustainability chapter, we applied ourself several constraints about the materials selection : single material parts, material 100 % recyclable only, etc. Some other constraints come from the context and the use of the product : resist UV, rain, temperature, | ||
| Line 1505: | Line 1523: | ||
| **Performance test** | **Performance test** | ||
| - | The technological performance of software was assessed using the Google Developers service [[https:// | + | The technological performance of software was assessed using the Google Developers service [[https:// |
| - | + | <WRAP center centeralign 750px> | |
| - | <figure figlabel41> | + | <table tlabel29> |
| - | {{ :: | + | < |
| - | < | + | ^ Performance Indicator ^ Screen Application ^ Mobile Application ^ |
| - | </ | + | | Overall Score | 92 | 90 | |
| - | <figure figlabel42> | + | | First Contentful Paint | 0.7s | 0.7s | |
| - | {{ : | + | | Time to Interactive | 1.4s | 1.5s | |
| - | < | + | | Speed Index | 1.0s | 1.1s | |
| - | </figure> | + | | Total Blocking Time | 10ms | 20ms | |
| + | | Largest Contentful Paint | 2.8s | 2.0s | | ||
| + | | Cumulative Layout Shift | 0.002s | 0 | | ||
| + | </table> | ||
| + | </WRAP> | ||