The Wireless Solar Powered DC Valve Controller (WSPDVC) project is an irrigation control system designed for hobby farms. The system is designed to give small farmers better control over their irrigation watering schedules by automatically turning on their sprinklers based on watering schedule times input into a website while being self powering. The system is split into three main systems, the irrigation nodes, the control system, and the website. The irrigation nodes are powered by solar panels and control the DC solenoid valves that control water flow. The control system hub connects the website to the irrigation nodes and back, passing along watering schedules from the website and any errors from the irrigation nodes. Both nodes have radio boards which allows them to communicate to each other wirelessly. Finally the web server connects to the control system through a Wi-Fi board and allows users to set new watering schedules, delete old ones, and see status updates from the irrigation nodes. This system did not reach it's final stage largely because of two obstacles. The batteries and converter that store energy from the solar panels and give it to the rest of the system needed several iterations for a functioning model, along with the final product having a piece that got so hot that it melted the soldering connecting some of the wires. The second obstacle was the communication between the radio board and Wi-Fi board in the control system. The two boards were set up to communicate via a physical UART connection, however coding the two different boards to synchronize properly required large investments of time to experiment and find what works. We were successful in getting the two to communicate, however the amount of time it took left little for other integration. From these obstacles we have gained experience and insight into what we could have done differently. Perhaps most importantly our group needed strategies to continue progress while a team member was missing. To combat this we have thought of two potential approaches, namely having secondary block champions that can fill in if the primary champion is absent and having an online software development platform that would allow all members to easily check on progress of code and become familiar with it. We have also learned that when creating project requirements, it is important to avoid dependencies that could create bottle necks within the project as the entire team waits for a single function to work.