SYNDICATE

Group Reflection: 

This operation was very interesting, the group applied their knowledge of gravitational force, terminal speed, the Tracker software and planetary acceleration in order to analyze data as training for Woodz Co. This lab experience was different from what was expected because one of our team mates was absent: Gurjot, but the rest of the group manage to collect the rest of the data. Everybody did almost did equal amounts of work, however because of Gurjot's absence on a crucial day, he did not meet up to expectations. The data collection was rushed because we did not have enough time; however, when working for Woodz Co, one has to learn how to deal with a shortage of time. In order to collect all the data, we gave up our personal time. Without Gurjot, the group finished trials 3, 4 and 5, with Gurjot, the group  worked on collecting data for trial 1 and 2. Everyone in the group worked on making the graphs, well, everyone except for Gurjot. Working on the graphs was a simple task; yet, it was very time consuming, something the group underestimated. Since Gurjot didn’t work on the graph, he worked on polishing the website. Parth and Jasmit worked on designing the website. To sum it up, Jasmit, Parth and Parmveer did equal amount of work, but Gurjot did slightly less work.

 

This task was disorganized. Sukhdev K. Bhatia of Woodz Co told us that we should "Learn to fly in free-fall." At first, we did not know what that meant; however, now we understand, this task was extremely stressful because of time constraints; as a result, we became disorganized which in turn, caused disunity. In free-fall, people are constantly falling, we were in somewhat of a free-fall in this task and now that we understand what Dr. Bhatia told us, we know that in order to avoid disunity and a sub-par result, we should always stay united and instead of falling to defeat, we should work hard and fly. 

 

Jasmit's Reflection:

In this task, we got too cocky and we learned from Woodz Co. exactly where that will get us. At first, we thought this task would take no time; however, we were wrong. There were many little things that we had to do in order to create the perfect report. Although we started out organized, the organization was not constant as an important member of the Syndicate was absent during two of our meets. This put a void in our system because we had time constraints and needed this member. However, because of the heroic effort put in by the other three, the project was safe and we did manage to get some of the project done within the time limit. Although we could not finish in time, we learned an important lesson; always compensate for an absence. Thinking that an absence would not make a difference is something Woodz Co. has taught us as wrong. An absence will always be a nuisance but it is how one deals with the absence that shapes them for greatness. Next time, I, personally as an alumnus of Woodz Co. would start completing the project early. Finally, I would suggest that our group learn to work more independently instead of being so dependent on collaboration. This project was all about collaboration; myself as the project facilitator did everything cohesively, I wish I had started on my own so I could have had more time to develop the best report to impress Woodz Co. 

 

Parmveer's Reflection:

This assignment was a tough case. With our previous case we got it easy and that got to our brains. When the assignment was presented by leader we thought it will be easy and nothing to worry about until the time comes. As time goes on we worked on the case approaching it with a simple brain, but a simple brain can't do much. As we realized that our assignment is not easy as we thought, we made a new plan, a more strategic plan. We all started working as a single unit. Day 1, I was away because of a secret assignment relating to Woodz Co's vs the Bondarzilas, but my group did not slow down they continued with the mission. They started their first trial  with one coffee filter and doing 8 runs to get all the information needed. Trial 2 was also started on day one but was not finished. Day 2, we faced the assignment hard with only three of us getting together during our break. We finished all the trials and started one the paper work, but another problem was encountered. The problem was that we didn't know what to do. With our teamwork and critical thinking we overcame this problem and moved on. The project managers did all the graphing and most of the lab. Sadly one the of Syndicates member was not found and no source of communication could be reached with that member. We assumed that the Bondarzilas had taken him but in truth he was injured. With our motivation, teamwork, critical thinking, creative thinking and the will of completing the mission we succeeded the assignment. We learned that when having a bad start it is not too late to do good, ups and downs come by very often by leave them behind and look towards the future and hope for the best.

 

Gurjot's Reflection:

I was not here on the final day, so I was not able to collect all the data with my group. To help my group, I worked on the parts of the lab: introduction, materials, procedure and group reflection. I have also helped my group with trial 1 and 2. Overall, I did slightly less work compared to the rest of the group members, but I did what I can in order to help them as much I can.

 

Parth's  Reflection:

In this project I was the Project Manager, Webmaster, Facilitator & Documenter. The reason why I have many roles in this project is because of the absence of a very important member of our Team.  Besides me there were two other Project Managers. I was responsible for dividing the work fairly so that everyone has a chance to do something and be an asset to this team.  As a documenter, I analyzed the Trial 4 & Trial 5. I used the Tracker Software to analyze the free-falling object (Coffee Filters) and record the data. As the project Facilitator, I helped members understand their respective learning processes. For example, a member of our Team didn’t know how find the Average Velocity from each runs and I assisted him in finding the Average Velocity. Finally, as the Webmaster, I was responsible for all the technical aspect of the website.  For example, Website Maintenance, Troubleshooting & improving the overall look of the website so that the viewers can easily navigate through the website. I was also accountable for uploading the operation report of Operation Terminal Velocity. We all were faced with many challenges in this Operation but we managed to pull the operation.