Skip to content

Commit 20edd71

Browse files
committed
docs added
1 parent 0e90690 commit 20edd71

4 files changed

Lines changed: 176 additions & 0 deletions

File tree

doc/sprint4/RMP.md

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
# Iteration 4 - Review & Retrospect
2+
**Project:** GLOW by Microsofties
3+
4+
---
5+
6+
## Meeting Details
7+
8+
- **When:** August 2, 2024
9+
- **Where:** Our House
10+
11+
---
12+
13+
## Process – Reflection
14+
15+
In this sprint we reflected on how the team worked together, what worked well, and what could be improved for smoother collaboration in future iterations.
16+
17+
---
18+
19+
### Decisions that turned out well
20+
21+
1. **Starting the sprint earlier**
22+
Beginning work ahead of schedule helped us identify blockers early and distribute workload more evenly.
23+
24+
2. **Aligning on priorities before starting work**
25+
Defining key tasks early ensured everyone focused on high-impact features first.
26+
27+
3. **Meeting more regularly**
28+
Frequent check-ins improved communication, allowed faster feedback, and sped up decision-making during UI/UX refinements.
29+
30+
---
31+
32+
### Decisions that did not turn out as well as we hoped
33+
34+
1. **Flexible deadlines for tasks**
35+
While flexible timelines reduced stress for individuals, it caused uneven progress across features, leading to integration delays and last-minute coordination.
36+
37+
---
38+
39+
### Planned changes
40+
41+
1. **Set clearer deadlines and checkpoints**
42+
Establish stricter internal deadlines and mid-sprint check-ins to prevent last-minute rushes.
43+
44+
2. **Improve estimation for unexpected work**
45+
Build a small buffer into sprint planning to manage surprise tasks without affecting critical features.
46+
47+
---
48+
49+
## Product – Review
50+
51+
### Goals and/or tasks completed
52+
53+
- **Historical Temperature Graph**
54+
Implemented and tested using real API data.
55+
56+
- **User Dashboard**
57+
Completed for displaying saved points and personalized data.
58+
59+
- **Docker Containerization**
60+
Application now runs fully using `docker-compose up`.
61+
62+
- **CI/CD Pipelines**
63+
Automated builds and deployments within 5 minutes confirmed after merging to `main`.
64+
65+
- **UI/UX Improvements**
66+
Enhanced color contrast, responsive design, and navigation; positive team feedback received.
67+
68+
- **Bug Fixes**
69+
Fixed theme switching, font consistency, and historical map display issues.
70+
71+
---
72+
73+
### Goals and/or tasks not completed
74+
75+
- **Time Range Filters**
76+
Deferred due to low priority and limited sprint time.
77+
78+
- **Archive & Download Data**
79+
Postponed to focus on core interactive features for this release.
80+
81+
---
82+
83+
## Meeting Highlights
84+
85+
- Continue starting early and aligning on priorities to maintain smooth progress.
86+
- Add time buffers for unforeseen bugs or last-minute tasks to avoid integration stress.
87+
- Refine CI/CD pipelines further to catch UI regressions early.
88+
- Next iteration will prioritize postponed features (e.g., time range filters, data export) while maintaining stability of core features.

doc/sprint4/burndown.pdf

264 KB
Binary file not shown.

doc/sprint4/schedule.pdf

1.1 MB
Binary file not shown.

doc/sprint4/sprint-04.review.md

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
# Iteration 4 - Review & Retrospect
2+
**Project:** GLOW by Microsofties
3+
4+
---
5+
6+
## Meeting Details
7+
8+
- **When:** August 2, 2024
9+
- **Where:** Our House
10+
11+
---
12+
13+
## Process – Reflection
14+
15+
In this sprint we reflected on how the team worked together, what worked well, and what could be improved for smoother collaboration in future iterations.
16+
17+
---
18+
19+
### Decisions that turned out well
20+
21+
1. **Starting the sprint earlier**
22+
Beginning work ahead of schedule helped us identify blockers early and distribute workload more evenly.
23+
24+
2. **Aligning on priorities before starting work**
25+
Defining key tasks early ensured everyone focused on high-impact features first.
26+
27+
3. **Meeting more regularly**
28+
Frequent check-ins improved communication, allowed faster feedback, and sped up decision-making during UI/UX refinements.
29+
30+
---
31+
32+
### Decisions that did not turn out as well as we hoped
33+
34+
1. **Flexible deadlines for tasks**
35+
While flexible timelines reduced stress for individuals, it caused uneven progress across features, leading to integration delays and last-minute coordination.
36+
37+
---
38+
39+
### Planned changes
40+
41+
1. **Set clearer deadlines and checkpoints**
42+
Establish stricter internal deadlines and mid-sprint check-ins to prevent last-minute rushes.
43+
44+
2. **Improve estimation for unexpected work**
45+
Build a small buffer into sprint planning to manage surprise tasks without affecting critical features.
46+
47+
---
48+
49+
## Product – Review
50+
51+
### Goals and/or tasks completed
52+
53+
- **Historical Temperature Graph**
54+
Implemented and tested using real API data.
55+
56+
- **User Dashboard**
57+
Completed for displaying saved points and personalized data.
58+
59+
- **Docker Containerization**
60+
Application now runs fully using `docker-compose up`.
61+
62+
- **CI/CD Pipelines**
63+
Automated builds and deployments within 5 minutes confirmed after merging to `main`.
64+
65+
- **UI/UX Improvements**
66+
Enhanced color contrast, responsive design, and navigation; positive team feedback received.
67+
68+
- **Bug Fixes**
69+
Fixed theme switching, font consistency, and historical map display issues.
70+
71+
---
72+
73+
### Goals and/or tasks not completed
74+
75+
- **Time Range Filters**
76+
Deferred due to low priority and limited sprint time.
77+
78+
- **Archive & Download Data**
79+
Postponed to focus on core interactive features for this release.
80+
81+
---
82+
83+
## Meeting Highlights
84+
85+
- Continue starting early and aligning on priorities to maintain smooth progress.
86+
- Add time buffers for unforeseen bugs or last-minute tasks to avoid integration stress.
87+
- Refine CI/CD pipelines further to catch UI regressions early.
88+
- Next iteration will prioritize postponed features (e.g., time range filters, data export) while maintaining stability of core features.

0 commit comments

Comments
 (0)