We are here at the end of a strenuous semester, our projects are mostly finished, exams start this week, and every single one of us is ready to get out of Dodge and enjoy our summers. As such, it is also time for evaluations, reflections, and thoughts on what we could have done better throughout the semester. In this particular reflection, I want to talk about the Mountain Dance and Folk Festival project my group and I have been working on. This has been a considerably long semester for all three of us, and that is only amplified by the fact this project has been wrought with hours of research and figuring out how to build a website. The research portion of this project took place primarily during the beginning of this semester, with a little bit of work going up until just after our spring break. In accordance to our contract, we wanted our research done and organized by March 11th, however that really didn’t come through, and we found ourselves organizing our research well after then. That said, the body of work of our research was pretty sound, so while we may have gone over our self-imposed deadline, it didn’t mean we were lacking in research. As we know of all three members of our group being procrastinators, I’ll be honest and say there isn’t much of a reason to try and defend our contract. While contracts by definitions are not just guidelines, you’ll find just about every student on earth is going to do what needs to be done to complete a project. If that project comes with a contract on which its students are held to requirements, students are likely to work to complete those requirements as best they can, just as we did. Did we complete our work as stated in our contract perfectly? No, we didn’t. Is that our fault? Absolutely, but given that our contracts were created and finalized by us, and we understand each other’s situations, we are going to treat this contracts with a sense of flexibility and leniency. Really the only thing we lived up to from our contract was what we actually had put onto our website. We stuck with our intended information and what we wanted to use to display that information. For instance, we stuck with our idea of using a timeline to display the history of the festival, and we stuck with using information on Bascom Lamar Lunsford and providing the games programming teams with useful information for their project as well. Our contract doesn’t state what would necessarily be on the pages of the website, just what the pages would be. We stuck with the Bascom Lamar Lunsford page, the Timeline of the festival, the music, the honor roll, and page on the dancing aspect of the festival. In that sense, we didn’t deviate from what our contract stated, yet because of the lack of what’s on the contract, the argument could be made that the contract is weak and thus our project is weak. We all stuck to what we would say we would do, more from verbal contracts than the written contract. We all are comfortable with holding ourselves accountable for any miscues or mistakes made, but there hasn’t been a problem with it yet.
A Somewhat Weak Defense of a Contract