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/12 11:39] – [Fourth sprint:] team1report:prm [2026/04/16 16:24] (current) – [Fifth retrospective - 2026-04-16] team1
Line 13: Line 13:
 /*Document the boundaries of your project. Document the product scope (the extent of what your project will produce) and the project Scope (summary of the work needed to produce it). Make sure you clearly define what is part of the project and what is outside of its scope, justifying as needed.*/ /*Document the boundaries of your project. Document the product scope (the extent of what your project will produce) and the project Scope (summary of the work needed to produce it). Make sure you clearly define what is part of the project and what is outside of its scope, justifying as needed.*/
  
-The scope of the project defines both the product to be developed and the work required to deliver it. In the case of Screen2Green, the main goal is to design and develop a functional prototype of a Smart Pot system that links smartphone screen-time behaviour to the condition of a living basil plant.+The scope of the project defines both the product to be developed and the work required to deliver it. In the case of Screen2Green, the main goal is to design and develop a functional prototype of a pot system that links smartphone screen-time behaviour to the condition of a living basil plant.
  
  
Line 19: Line 19:
  
  
-From a project perspective, the scope includes all activities (see {{ref>WBS}} for the Work Breakdown Structure for the project) necessary to research, design, develop, and document the prototype. This involves background research such as indoor herb cultivation, hydroponics, smartphone usage and mental health. It also includes concept generation, selection of materials and components, development of hardware and software, testing, evaluation, and the production of all required academic deliverables, such as the report, presentations, poster, flyer, and supporting documentation.+From a project perspective, the scope includes all activities (see Figure {{ref>WBS}} for the Work Breakdown Structure for the project) necessary to research, design, develop, and document the prototype. This involves background research such as indoor herb cultivation, hydroponics, smartphone usage and mental health. It also includes concept generation, selection of materials and components, development of hardware and software, testing, evaluation, and the production of all required academic deliverables, such as the report, presentations, poster, flyer, and supporting documentation.
  
  
  
 +<WRAP centeralign>
 <figure WBS> <figure WBS>
 {{ :report:bwc.jpg |WBS for Screen2Green}}<caption>WBS for Screen2Green</caption> {{ :report:bwc.jpg |WBS for Screen2Green}}<caption>WBS for Screen2Green</caption>
 </figure> </figure>
 +</WRAP>
 +
  
  
Line 131: Line 134:
  
  
-In order to assess quality, the team defined the following general metrics:+In order to assess quality, the team defined the general metrics listed in Table {{ref>quality_metrics}}.
  
 <table quality_metrics> <table quality_metrics>
Line 219: Line 222:
  
  
-<WRAP center round box 60%>+<WRAP centeralign>
 <figure risk_matrix> <figure risk_matrix>
 {{ :report:risk_matrix.png?600 |}} {{ :report:risk_matrix.png?600 |}}
Line 277: Line 280:
 | 4  | Mar 26 – Apr 1  | Refining, refactoring, developing & testing | 0 | Finished | 45.16 % | | 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 % | | 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 |  | | 8  | Apr 23 – Apr 29 | Finalizing the components & materials list | 1 | To do |  |
 | 9  | Apr 30 – May 6  | Refining the interim | 1 | To do |  | | 9  | Apr 30 – May 6  | Refining the interim | 1 | To do |  |
Line 315: 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. 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 ==== ==== Sprint Outcomes ====
-=== First sprint: ===+=== First sprint ===
 By the end of the sprint, every task was completed and the team evaluated the task weight to be a healthy number. After each member researched and reported on their given fields, the team could focus on making a sprint plan. By the end of the sprint, every task was completed and the team evaluated the task weight to be a healthy number. After each member researched and reported on their given fields, the team could focus on making a sprint plan.
  
-=== Second sprint: ===+=== Second sprint ===
 The backlog consisted of tasks regarding the deliverables, subject related assignments and refactoring prior research. The reason behind the latter is because the reports were written unprofessionally and were saved in a separate environment. By the end of this sprint, all the research got refactored into the Wiki. There was an exponential growth of amount of tasks done per day, but everything was finished before the retrospective. The backlog consisted of tasks regarding the deliverables, subject related assignments and refactoring prior research. The reason behind the latter is because the reports were written unprofessionally and were saved in a separate environment. By the end of this sprint, all the research got refactored into the Wiki. There was an exponential growth of amount of tasks done per day, but everything was finished before the retrospective.
  
 The following sprints will have more focus on proper communication, this is because some tasks were done without having their status updated in Jira and because there was low engagement off-campus. The following sprints will have more focus on proper communication, this is because some tasks were done without having their status updated in Jira and because there was low engagement off-campus.
  
-=== Third sprint: ===+=== Third sprint ===
 The team felt like they were behind on tasks and internal discussions, so the third sprint focused on lots of research, deliverables and internal tasks. Out of a total of 35 tasks with  considerable weight, 32 were finished and the smallest ones were transferred to next sprint. The team is extremely satisfied with how this sprint ended. Team 1 managed to finish important discussions and decide on important factors of the project, leading to everyone being on the same basis. The team felt like they were behind on tasks and internal discussions, so the third sprint focused on lots of research, deliverables and internal tasks. Out of a total of 35 tasks with  considerable weight, 32 were finished and the smallest ones were transferred to next sprint. The team is extremely satisfied with how this sprint ended. Team 1 managed to finish important discussions and decide on important factors of the project, leading to everyone being on the same basis.
  
Line 332: Line 339:
 === Fifth sprint === === 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. 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 ==== ==== Sprint Evaluations ====
 === First retrospective - 2026-03-05 === === First retrospective - 2026-03-05 ===
Line 400: Line 412:
   * Stop doing:   * Stop doing:
     * /     * /
 +
 +=== 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:
 +  * 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 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 should the team:
 +  * Keep doing:
 +    * 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:
 +    * /
 +  * Stop doing:
 +    * 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 ==== ==== Summary ====
  
  • report/prm.1775990366.txt.gz
  • Last modified: 2026/04/12 11:39
  • by team1