-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathblog_details_group_reflection.html
352 lines (288 loc) · 24.9 KB
/
blog_details_group_reflection.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
<!doctype html>
<html class="no-js" lang="zxx">
<head>
<meta charset="utf-8">
<meta http-equiv="x-ua-compatible" content="ie=edge">
<title>栗 KURI 栗 team's website</title>
<meta name="description" content="">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="shortcut icon" type="image/x-icon" href="assets/kuri photos/BW-darkx150px.ico">
<!-- CSS here -->
<link rel="stylesheet" href="assets/css/bootstrap.min.css">
<link rel="stylesheet" href="assets/css/owl.carousel.min.css">
<link rel="stylesheet" href="assets/css/slicknav.css">
<link rel="stylesheet" href="assets/css/animate.min.css">
<link rel="stylesheet" href="assets/css/magnific-popup.css">
<link rel="stylesheet" href="assets/css/fontawesome-all.min.css">
<link rel="stylesheet" href="assets/css/themify-icons.css">
<link rel="stylesheet" href="assets/css/slick.css">
<link rel="stylesheet" href="assets/css/nice-select.css">
<link rel="stylesheet" href="assets/css/style.css">
<link rel="stylesheet" href="assets/css/kuri_style.css">
<link rel="stylesheet" href="https://www.w3schools.com/w3css/4/w3.css">
</head>
<body>
<!-- Preloader Start -->
<div id="preloader-active">
<div class="preloader d-flex align-items-center justify-content-center">
<div class="preloader-inner position-relative">
<div class="preloader-circle"></div>
<div class="preloader-img pere-text">
<img style="width: 35px; height: 35px;" src="assets/img/kuri photos/Kuri_BW-light.ico" alt="">
</div>
</div>
</div>
</div>
<!-- Preloader Start -->
<header>
<!-- Header Start -->
<div class="header-area header-transparent">
<div class="main-header">
<div class="header-bottom header-sticky">
<div class="container-fluid">
<div class="row align-items-center">
<!-- Logo -->
<div class="col-xl-2 col-lg-1 col-md-1">
<div class="logo">
<a href="index.html"><img style="width: 273px; height: 150px;" src="assets/img/kuri photos/Inline Logo BW-lightx150px.png" alt=""></a>
</div>
</div>
<div class="col-xl-8 col-lg-8 col-md-8">
<!-- Main-menu -->
<div class="main-menu f-right d-none d-lg-block">
<nav>
<ul id="navigation">
<li><a href="index.html">Home</a></li>
<li><a href="about.html">About us</a></li>
<li><a href="blog.html">Blogs</a>
<!-- <ul class="submenu">
</ul> -->
</li>
<li><a href="contact.html">Contact</a></li>
</ul>
</nav>
</div>
</div>
<!-- Mobile Menu -->
<div class="col-12">
<div class="mobile_menu d-block d-lg-none"></div>
</div>
</div>
</div>
</div>
</div>
</div>
<!-- Header End -->
</header>
<main>
<!-- Hero Start-->
<div class="slider-area slider-bg ">
<div class="single-slider d-flex align-items-center slider-height2 ">
<div class="container">
<div class="row">
<div class="col-xl-12">
<div class="hero-cap text-center pt-50">
<h2>Group Reflection</h2>
</div>
</div>
</div>
</div>
</div>
<!-- Slider Shape -->
<div class="slider-shape d-none d-lg-block">
<img class="slider-shape1" src="assets/img/hero/top-left-shape.png" alt="">
<img class="slider-shape2" src="assets/img/hero/right-top-shape.png" alt="">
<img class="slider-shape3" src="assets/img/hero/left-botom-shape.png" alt="">
</div>
</div>
<!--Hero End -->
<!--================Blog Area =================-->
<section class="blog_area single-post-area section-padding">
<div class="container">
<div class="row">
<div class="col-xl-12 posts-list">
<div class="single-post">
<div class="w3-content w3-display-container">
<img class="mySlides" src="assets/img/blog/group_reflection.jpg" style = "width:100%">
</div>
<div class="blog_details">
<h2>Group Reflection of team members
</h2>
<div class="testimonial-founder d-flex align-items-center mb-30">
<div class="founder-img">
<img class="avapic" src="assets/img/about us pic/img-3.png" alt="">
</div>
<span class = "feedbackname">Vo Tuong Minh</span>
</div>
<div class="row">
<div class="col-lg-12">
<blockquote class="generic-blockquote">
During those four weeks, Kuri team members worked very well together given the short period to complete our report paper, website, and project demo. Communication between us was good and very effective. Our planning was very detailed, with deadlines for each week. Overall, progress was going well for all three aspects of this assignment: Writing, Web development, and Game development.
<br><br>However, our planning and scheduling could still be improved to be more professional, utilizing more tools provided by the school such as Canvas, Outlook, and GitHub. Our skill working together on GitHub and version controlling our project and website was still somewhat limited due to our lack of experience working on real-world projects.
<br><br>As the lead game developer, one thing that came as a surprise to me was the steep learning curve of our chosen game development framework. From this, I have concluded that for future projects, I would need more careful technical preparation and research before committing to a project.
<br><br>As the team’s leader and project manager, I have learned that communication is incredibly important when working in a team. Having a communication breakdown, such as a member being unresponsive or incoherent scheduling and tasks between members, is the worst thing that can happen to a team. Hence, the first meeting as a group plays a key role in bringing the members together, as concerns can be addressed preemptively and rules can be set openly and clearly ahead of any commitment.
</blockquote>
</div>
</div>
<div class="testimonial-founder d-flex align-items-center mb-30">
<div class="founder-img">
<img class="avapic" src="assets/img/about us pic/img-4.jpg" alt="">
<span class = "feedbackname">Nguyen Hoang Linh</span>
</div>
</div>
<div class="row">
<div class="col-lg-12">
<blockquote class="generic-blockquote">
Throughout my time working as a Kuri member, I could see the improvement in the way our team worked each week. I think the key point to this is that the communication between our members had become better throughout the project. The goals of each week had been divided into smaller tasks so that each member could know exactly what tasks they needed to finish. At the end of each week, we informed each other of our progress and at the beginning of next week, we set our detailed planning and deadlines. In general, all three groups had completed their work really well for this assignment. For the game development, Mike had completed his beta version of the game and was ready to release it soon for beta testing. The game worked amazingly well and the gameplay was really interesting. For the web development that I was in charge of as the leader, I could see that there was still some missing communication between me and Huy, the other web developer, which led to the delay of the website. I could also see that we still had certain issues and problems working as a team on Github, which led to several unnecessary conflicts. However, we had worked on and resolved that issue, so the website was up and running smoothly. Last but not least, the writing group had spent a lot of time writing and editing the final report along with creating the slides and script for the standup meeting. The work process of Kuri as well as the quality of each team’s work were fascinating. Overall, this was a great opportunity for me to learn more by working with these people.
</blockquote>
</div>
</div>
<div class="testimonial-founder d-flex align-items-center mb-30">
<div class="founder-img">
<img class="avapic" src="assets/img/about us pic/img1.jpg" alt="">
</div>
<span class = "feedbackname">Doan Yen Nhi</span>
</div>
<div class="row">
<div class="col-lg-12">
<blockquote class="generic-blockquote">
On one hand, various things went very well throughout the weeks we worked together. Firstly, our communication was quite successful: we responded regularly and quickly to each other’s messages, and we updated our progress weekly so that our team leader and other members of Kuri could keep track of our work. Secondly, we were usually on time with our weekly deadlines, even though we sometimes needed to remind each other of the deadlines and tasks.
<br><br>On the other hand, there were things that we also needed to work on. Since we were not very proficient in using GitHub as a team, we were not too organized and able to use the tool to its full potential. Hence, in the future, we will need to discuss how we will use GitHub as a team at the very beginning of the project so that our workflow on GitHub can be more smoothly.
<br><br>While completing this group assignment, one thing that surprised me was how much our team leader had planned for the project. He told me that he had several backup plans and he also kept a lot of options open so that we can be flexible. This made me realize how important project planning is and how detailed project planning had helped us succeed in the project.
<br><br>From this project, I have learned that for groups to be successful, communication is extremely significant. For members not to get lost on what the team is working on and to know exactly what their tasks and responsibilities are, we need to communicate frequently and update each other on our progress. Members should also ask questions or ask for help when needed so that other members can support them or solve it together.
</blockquote>
</div>
</div>
<div class="testimonial-founder d-flex align-items-center mb-30">
<div class="founder-img">
<img class="avapic" src="assets/img/about us pic/img-2.png" alt="">
</div>
<span class = "feedbackname">Nguyen Nhat Huy</span>
</div>
<div class="row">
<div class="col-lg-12">
<blockquote class="generic-blockquote">
After working with our team Kuri for several weeks, I noticed that every single member had worked really hard. We learned a variety of new things every week, so our group’s productivity improved considerably, and I think that this was due to our good communication. Our leader assigned tasks to each member logically based on their ability and skills. Furthermore, the tasks for each week were very clear and divided into many subtasks so that we could do them step by step to accomplish our aims. Thanks to this clear and logical strategy, all of the members had worked successfully on this assignment. Regarding web development, despite my lack of knowledge, Linh and I managed to deliver a website that had all the features needed for our group project. Linh did his job perfectly while I was sometimes still confused with Github and writing HTML. Next, game development, which was led by Mike, was one of the most important parts of our project. Although there were some bugs in the game, it still worked out the way our team wanted it to. Lastly, the writing group tried their best to write and deliver a final report that was of high quality, which allowed us developers to focus on our tasks. In conclusion, our team has learned from each other and improved ourselves significantly, and we were able to not only explore more about the IT field but also about collaboration and teamwork.
</blockquote>
</div>
</div>
<div class="testimonial-founder d-flex align-items-center mb-30">
<div class="founder-img">
<img class="avapic" src="assets/img/about us pic/img-5.jpg" alt="">
</div>
<span class = "feedbackname">Do Duc Manh</span>
</div>
<div class="row">
<div class="col-lg-12">
<blockquote class="generic-blockquote">
We worked together for four weeks and everything went by very fluently. Our weekly plans were usually finished in time, and we had face-to-face group meetings mostly every week so we could know the up-to-date progress of each group. The products of our work were of high quality: The game had a retro 8-bit design with moderately challenging gameplay, the website had a visually pleasant format and styling, and the report progress went well as everything was finished in the middle of week 12.
<br><br> However, we did not work on GitHub very efficiently: On some occasions, a member forgot to pull the files from our online GitHub repository, which caused a conflict when they pushed their version, and some members needed to send their files to another member to push the files. We can improve this by remembering to pull the files while working on the same branch or create many branches for members to work on.
<br><br>A surprising aspect of our group was that our team could progress well. Although we had only known each other since the start of this course, our communication and workflow were good enough to help us finish our jobs before the small deadlines that we created for ourselves within each group.
<br><br>Effective communication is what I have learned from working in a group. It can boost productivity because it can make each member feel more responsible for their work. Good communication can also boost morale and be useful when someone in the group needs help.
</blockquote>
</div>
<div class="col-xl-12">
<div class="hero-cap text-center pt-50">
<h2 class="vkl">Kuri’s group reflection</h2>
</div>
<p class="aboutusp"> <br><br>  Within these four weeks, various aspects of the project went by smoothly. To begin with, none of the teams faced any significant problems with their respective tasks; all teams were able to finish the core functionalities and features of their work with good quality. Additionally, since we were quite strict with deadlines, Kuri members usually submitted their work on time. The second aspect that went well is our scheduling and team meetings: every member remembered and attended most of the meetings, even if they could not be there in person, and when a member missed a meeting, we informed them of the main points through our group chat. Our scheduling and meetings were successful because we set the schedule, including the deadlines and meetings, clearly for each week using the Outlook calendar; hence, members could easily track and know the schedule for each week. Lastly, we did not encounter any serious conflicts between members since everyone worked very well together. We listened to and respected each other, and we kept an open mind to welcome other members’ ideas and opinions.
<br><br>  Nevertheless, there were still elements that needed to be improved. As mentioned and discussed by most of the members, our team had some difficulties with collaboration on GitHub since we were not very experienced with this tool. Another part of our project that did not go well is the bugs in our game. Even though we did not have any major issues with the fundamentals of the game, we still had a lot of bugs. Moreover, our game could not run on iOS and Mac devices; therefore, this is an element that we will need to figure out in the future if we want to continue with this project.
<br><br>  While working on the project, a few factors surprised all of us. Firstly, our choice of the game framework (Phaser) was harder and the learning curve was steeper than expected, so the game development group had to investigate Phaser and JavaScript before the project officially started. Regarding the website, the chosen template looked pleasant but working with it was not the best-case scenario for us. There were no clear instructions or any documents to guide us through using the template, and the .css and .js files of the template were both minimized. Therefore, it took us some time to understand the code of this template before we could use it. The last surprising factor - in a positive way - was how well we worked together. Even though we first met each other through this class at RMIT, we completed our weekly plans effectively and did not have any major disagreement within our group.
<br><br>   Working with each other helps us attain new knowledge on how a team should operate. We recognize how important the first meeting is, as it can set the workflow and determine the working vibe of the team. We also realize that to lead others, we should be an example for them to follow so that we can create an encouraging working environment. For instance, when a member does not know how to use GitHub as a team, the leader should directly demonstrate and show them how to do it. Lastly, a leader should also utilize each member’s abilities and strengths and delegate suitable tasks to every member to get the best performance out of the team.
</p>
</div>
</div>
<div class="navigation-top">
</div>
<div class="navigation-area">
<div class="row">
<div
class="col-lg-6 col-md-6 col-12 nav-left flex-row d-flex justify-content-start align-items-center">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!--================ Blog Area end =================-->
</main>
<footer>
<!-- Footer Start-->
<div class="footer-area">
<div class="container">
<div class="footer-bottom">
<div class="row d-flex justify-content-between align-items-center">
<div class="col-xl-9 col-lg-9 ">
<div class="footer-copy-right">
<p><!-- Link back to Colorlib can't be removed. Template is licensed under CC BY 3.0. -->
Copyright ©<script>document.write(new Date().getFullYear());</script> All rights reserved | </p>
</div>
</div>
<div class="col-xl-3 col-lg-3">
<!-- Footer Social -->
<div class="footer-social f-right">
<a href="https://github.com/kuri-team"><i class="fab fa-github"></i></a>
</div>
</div>
</div>
</div>
</div>
</div>
<!-- Footer End-->
</footer>
<!-- Scroll Up -->
<div id="back-top" >
<a title="Go to Top" href="#"> <i class="fas fa-level-up-alt"></i></a>
</div>
<!-- JS here -->
<!-- All JS Custom Plugins Link Here here -->
<script src="./assets/js/vendor/modernizr-3.5.0.min.js"></script>
<!-- Jquery, Popper, Bootstrap -->
<script src="./assets/js/vendor/jquery-1.12.4.min.js"></script>
<script src="./assets/js/popper.min.js"></script>
<script src="./assets/js/bootstrap.min.js"></script>
<!-- Jquery Mobile Menu -->
<script src="./assets/js/jquery.slicknav.min.js"></script>
<!-- Jquery Slick , Owl-Carousel Plugins -->
<script src="./assets/js/owl.carousel.min.js"></script>
<script src="./assets/js/slick.min.js"></script>
<!-- One Page, Animated-HeadLin -->
<script src="./assets/js/wow.min.js"></script>
<script src="./assets/js/animated.headline.js"></script>
<script src="./assets/js/jquery.magnific-popup.js"></script>
<!-- Nice-select, sticky -->
<script src="./assets/js/jquery.nice-select.min.js"></script>
<script src="./assets/js/jquery.sticky.js"></script>
<!-- contact js -->
<script src="./assets/js/contact.js"></script>
<script src="./assets/js/jquery.form.js"></script>
<script src="./assets/js/jquery.validate.min.js"></script>
<script src="./assets/js/mail-script.js"></script>
<script src="./assets/js/jquery.ajaxchimp.min.js"></script>
<!-- Jquery Plugins, main Jquery -->
<script src="./assets/js/plugins.js"></script>
<script src="./assets/js/main.js"></script>
<script>
var slideIndex = 1;
showDivs(slideIndex);
function plusDivs(n) {
showDivs(slideIndex += n);
}
function currentSlide(n) {
showDivs(slideIndex = n);
}
function showDivs(n) {
var i;
var x = document.getElementsByClassName("mySlides");
if (n > x.length) {slideIndex = 1}
if (n < 1) {slideIndex = x.length}
for (i = 0; i < x.length; i++) {
x[i].style.display = "none";
}
x[slideIndex-1].style.display = "block";
}
</script>
</body>
</html>