Reflection on Team Progress (snippet from our thoughts at end of Semester 1)
Overall, our team has most definitely progressed at an effective rate to get our overall goals by the end of next semester. One of the major goals we made for this semester was purchasing our compressor and turbine motor by Winter Break so that we could have them by the time we get back next semester. We already purchased each of these components and have both of them in hand, so we accomplished that goal. Another goal we made was to have preliminary calculations and equations completed to be able to analyze our system once we integrate each subsystem (compressor/pressure vessel, heat exchanger, turbine/motor). We also accomplished this and should be on the right track to fully analyze our system once we get everything integrated together. Hopefully, this track that we are on stays at a steady rate where we can complete our prototype and we are able to fully test it and then analyze the real-world applications.
Our team structure, roles, and responsibilities have fared really well over the first semester. We tried to break down the team structure into areas that require a similar amount of work but are also something that interests the group or individual. Most of the roles have stayed the same that we initially assigned, but some have slightly changed to better suit the needs of the team. Each person should have a set role now that they carry out throughout the next semester. This has allowed us to complete everything that was necessary on time.
In regards to the goal-setting activity, we ranked the following as our three most important goals: 1) want to be proud of the outcomes of the project, 2) want to learn new topics/concepts/skills throughout the project, and 3) want to complete all deliverables for the class in a timely manner. Ultimately, we, as a team, most definitely have the actions and behaviors that are in alignment with these goals (along with each of the other goals since each of the 12 goals were still a priority no matter the ranking). Without a doubt, we have learned numerous concepts and skills throughout the project in order to best complete our project, which has helped us complete all of our deliverables in a timely manner. The reason we wanted to make sure we completed everything in a timely manner is because we wanted to make sure we were on the right track to accomplish the project goals we have set for ourselves, rather than having to cram everything in the last month or two of next semester. Additionally, we are proud of the progress we have made so far because we believe that our project can make a legitimate difference to society. Hopefully, at the conclusion of next semester, we have a working prototype that we are thrilled with.
Reflection on Team Structure
Having the team structured with three subsystem teams was an effective strategy to be able to allow each individual to allocate time towards a specific aspect of the project design rather than each person having to fully consider and work with each subsystem. This allowed us to specialize in more microscopic design decisions which benefited the overall design of our CAES system. Three subsystem teams in total were an effective amount (more would have been too many), as we worked together in small groups but also were not working individually so there were important elements of a team collaboration going on.
Creating specific roles such as project manager, budgeteer, and editors, led to a more cohesive structure for team scheduling and processing. We allocated these relatively early in the project so we clearly understood who was responsible for certain tasks. Early in the process of having subsystem teams, we did not have set subsystem team leads which led to a lack of communication between the subsystem teams at times. We then added subsystem team leads and made more of an emphasis to communicate between the different subsystem teams to make sure that we were on the same page. Additionally, we allocated tasks towards the end of our projects such as instrumentation and data acquisition and were responsible for our final deliverables whenever certain subsystem prototyping was completed. Having these tasks broken up created a structure for all project elements to be considered and focused on. We also allocated tasks for each deliverable so that we made sure each required topic was covered.
Our project was completed at a pace about that what we expected going into the project. We completed everything that we set out to do at the beginning of the project and maintained a pace close to that of what we had set in our project timelines as the two semesters went along. We utilized a Gantt chart to keep track of tasks that we needed to complete and when we wanted to complete them. We started this relatively early in the project but did not utilize it for the first month or so, which would have been helpful to keep track of initial deadlines. Once we started focusing more on schedule, it led to a more fluid process. Additionally, we did not set actual dates for the scheduling in the Gantt chart during the first semester. We created a more detailed schedule process during the second semester which was even more beneficial since we could keep track of actual internal deadlines rather than vague dates. If we started the project over again, we would have started this process earlier.
On our next long-term project, we would make sure to emphasize communication and scheduling. If each team member knows exactly what role and responsibilities they are responsible for then the project will flow smoothly. Also, communication between groups and individuals is very important, especially when their work is tied or influenced by others. Having weekly check-ins puts everyone on the same page and helps contribute to healthy communication within the whole team. Gantt charts and internal deadlines keep the project on track and emphasize a gradual process rather than doing the project in spurts. Having a detailed schedule is crucial in a successful project and we would consider having a slightly more comprehensive schedule. This would allow for easier completion of the deliverables and more iteration to make sure our updates are as good as possible.
Our overall team leadership was aided by the expertise of Professor Van Asselt. In future projects, it is helpful to have a knowledgeable team member lead the team in the right direction and help guide members in the next steps. Even if this member doesn’t have experience directly in the project at hand, it is helpful that they know the resources and general project management skills.
