Team Status Report 2/22

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

One of our risks right now is making sure that we will be ready for relevant builds in a reasonable timeframe. As Professor Sullivan mentioned during our meetings, it is important to order parts with significant time due to potential shipping delays. It will be important to place orders for our project early this week, presumably after having our meeting with our staff on Monday to confirm our feedback from the presentation, so that we can have our relevant hardware accessible. After the parts are ordered, we should make sure to actively track parts, including over spring break, to allow for pivoting if a part is heavily delayed.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

All of our existing design goals are aligned with what we presented at the design presentation. We did more heavily spec out our existing design decisions for the design presentation, including selecting our audio processing style, specific hardware decisions (e.g. using the Arduino Nano BLE), and lyric sourcing mechanisms from our potential options. We also prepared a more in depth GANTT chart than we had for the first presentation. However, we are prepared to use for potential feedback from our design presentation to adjust accordingly next week.

Leave a Reply

Your email address will not be published. Required fields are marked *