Team Status Update for 02/22

This week has been one of setbacks and stalls. Rhea’s progress stalled due to illness and my own progress stalled due to technical difficulties. However, Rhea’s progress is more critical. She has fallen very far behind in terms of tag-anchor communication deliverables. This poses the most severe risk to the project.

To manage this risk, Udit and I will both be setting aside our previous deliverables to work with Rhea on tag-anchor communication. The current anchor-server network difficulties are primarily due to inbuilt issues with Linux, while the tag-anchor communication poses more complex challenges of understanding and implementing custom software. Therefore, we have deemed the anchor-server problems as lower priority to be solved later.

As a result of this, we have also scaled down our mean viable product. Our goal is to get one tag communicating with one anchor, presuming that we will be able to scale the tag-anchor and anchor-server networks up as needed. This change was required to keep the project manageable in the face of unforeseen difficulties while still delivering a viable product. Going forward, we will be aiming for more granular, design-focused deliverables to ensure incremental, consistent, and meaningful progress.

Leave a Reply

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