You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/sprint3/iteration-03.plan.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ In addition to their specific roles, all team members have a collective responsi
36
36
37
37
#### Epic 3: Deployment
38
38
39
-
**Team Members:** Masahisa
39
+
**Team Members:** Masahisa
40
40
41
41
- Create a dockerfile such that our application can be run on a docker image with application setup being done automatically.
42
42
- Ensure that our application’s docker image runs on a VM instance accessible on the web.
@@ -59,6 +59,7 @@ In addition to their specific roles, all team members have a collective responsi
59
59
- Define tasks and responsibilities for each team member
60
60
61
61
-**Stand up meeting**:
62
+
62
63
- Location: Online or in-person depending on members availability
63
64
- Time: Every Tuesday from 12 pm to 1 pm, Thursday and Sunday from 9 pm to 10 pm
64
65
- Purposes
@@ -107,11 +108,10 @@ In addition to their specific roles, all team members have a collective responsi
107
108
108
109

109
110
110
-
- Furthermore, we will implement a Burndown Chart, which will be included as `burndown.pdf` by the end of the sprint. This chart will also feature comments on the sprint's progress and a velocity comparison.
111
-
- Below is an example Burndown Chart from Sprint 0:
112
-
113
-

111
+
- Furthermore, we will implement a Burndown Chart, which will be included as `burndown.pdf` by the end of the sprint. This chart will also feature comments on the sprint's progress and a velocity comparison.
112
+
- Below is an example Burndown Chart from Sprint 0:
114
113
114
+

115
115
116
116
## 2. Product
117
117
@@ -128,19 +128,20 @@ In addition to their specific roles, all team members have a collective responsi
0 commit comments