Software
-Personal computers proved to be a problem with Revit. Several team members had to reinstall Revit several times before it was able to work properly on their own device. This added inconvenience to the initial stage of the project and set us back a bit
-None of the team members were particularly experienced with Revit, so learning in the labs and using Anthony for help kept us on track during the project.
File Management
-Sharing various types of documents between the team was a struggle. We originally were going to use exclusively the M-Drive, but quickly realized Google drive would be easier for using non-Tech computers. We decided to switch to Google Drive, only to realize that saving numerous Revit and CAD files to Google Drive is more problematic than using the M-Drive. We settled on splitting files between the M-Drive and Google Drive with Google hosting our documents, photos, and presentations while the M-Drive held our program files.
Scheduling
-We started our project in the middle of flu season, so many of the team was very sick for weeks leading us to get off to a very rocky start in terms of communication and actual progress. After the flu, spring break happened, which allowed us to refocus. We found it hard to meet in person due to our differing school, work, and activity schedules. Due to this, most of our communication happened on discord.
Michigan Tech VPN
-The MTU VPN was our main link to the M-Drive while not at a school computer. The VPN proved very unreliable, and not up to the task of working remotely with Revit and Navisworks. This caused a lot of frustration early on as we attempted to work on our own computers. Using Navisworks and the VPN resulted in crashing the program every time, so we had to complete some work on school computers.