Our classroom project has gotten to a slow but sure start this week. Since my team hadn’t already set up the procedure for governing progress on the site, it was generally freely-run by the individual teams for the first few days. Still, by the end of the week our group had determined what duties we were responsible for and became far more effective in our leadership, and I believe this trend will continue in the upcoming weeks as we become more comfortable with our tasks. On Monday, our team was a bit confused with where to start, but with some thought we figured out several things that needed to be done. Beyond the obvious gantt chart, we were responsible for quick classroom presentations on Mondays, Wednesdays, and Fridays. Thus, we needed a written procedure by which we would deliver these presentations. Both Patrick and I typed the procedure for these meetings, making sure it covered key points on each group’s progress. After creating this procedure we realized it was also necessary for us to communicate between individual teams, and so Patrick and I also created a sheet for determining the questions to be asked when meeting with the other teams. Meanwhile, Stephanie and Adria were creating a sheet for people to post client questions on Google docs as well as formatting the gantt chart. By the end of the day, I established an online meeting Tuesday at 7:30 to organize the gantt chart before the following Wednesday. Sadly, I stayed up all night Monday working on another class project, catching a terrible cold that left me sick for the next two days. I missed both the meeting and the next day of class, but the rest of my group still made time for both and for that I am grateful. By Friday I was feeling much better, and in class was able to help quite a deal with communication between groups. For one, I found that the design team was preparing many color schemes but only one layout for the client, so I suggested we provide several layout designs, which many others agreed with. Also, from conversation with the backend programming team I found there was to be a website portal page for administrative purposes, of which the design team knew nothing about. I then informed them of this device so that they could create layout roughs for it as well, and Adria adjusted the gantt chart for their team accordingly. Other than that, I took time to oversee each group’s individual progress and was glad to see how everyone was coming along. In the future the documents and testing team will need more specific details on how the portal system will work from the backend programming team, which I will help coordinate. Beyond that, our team will continue to do flesh out its operations, and though we haven’t decided yet, some sort of rotation cycle will be used to keep track of progress and aid communication.