This week, our team gave our SLDR presentation! We received lots of helpful feedback, and were asked some difficult questions. Overall, the presentation went well, and we appreciate the feedback and questions from the audience.

In the next semester, we plan on continuing our prototype design by implementing planned features that we could not get to in the initial prototype for PID, such as iOS support and integration with the Bluetooth Beacon system. We will also implement changes based on the feedback we received during our presentation, and will be sure to come up with adequate answers for some of the challenging questions that our audience asked us. This will involve our team researching and developing the business and financial case for our in-car payment solution more in the coming semester.

This week, our team finished our rough draft of our System-Level Design Review (SLDR) report and presentation, which we will present this coming week. We gave our draft presentation to the class for peer review, and received lots of good feedback on improvements we could make. One important piece of feedback we received is that our presentation needs to talk about the different potential use cases for the product.

Over the next week, we plan on incorporating the feedback we received from the peer review and our sponsor meetings into our presentation, so that we can fix issues and make improvements. We will also continue to practice our presentation to make sure we’re all comfortable with the material and ready to present it. We will continue working on our SLDR report as well, and will make sure it’s in good shape before submitting it to our sponsor.

This week, we presented out first prototype! We demonstrated our application’s functionality on both the merchant and customer sides, complete with a working system for transferring menu and order information over Bluetooth. The judges seemed impressed by our prototype, and we appreciate their feedback. We received useful comments from the people attending the event, and have created an action plan to handle this feedback. Our next main goal is to work towards the System Level Design Review. We will update our roadmap to account for this, and have started allocating sections of it to team members.

This week, the team continued utilizing the scrum methodology to divide tasks and drive the project forward. This has allowed the team to work more efficiently and progress has been made on the prototype, particularly with the UI/UX for the customer screens as well as establishing a bluetooth connection. The team also met with the sponsor for feedback on their current progress, as well as making sure their vision aligned with the sponsor for what should be included in the prototype for inspection day.

Over the weekend, the team plans to meet in person in order to effectively finish the first stage of the prototype and prepare for the presentation. The team does not anticipate any setbacks and is excited to demonstrate their prototype!

This week, we gathered together all of our ideas for the prototype and began development. We assigned tasks to each team member, and decided on using Github issues to keep track of everyone’s progress during this initial prototype process. We also formalized all of our new team roles for this agile development process to help make sure that we can all communicate what needs to be done efficiently.

Over the next week, we plan to continue working on the prototype to get it done by the November 16th deadline. Every Tuesday and Thursday, we will have scrum check-in meetings to resolve issues and make sure everyone is on track and making good progress.

This week, our team worked on developing our plan for prototype inspection day. We discussed our plan with our sponsor to make sure we were all on the same page. Our preliminary plan for our prototype involves demonstrating the Bluetooth connection between the customer mobile application and the merchant device, and the automatic transfer of JSON-formatted data between them, which can be modified on the device and sent back.

We also changed up some of our team roles this week! Shaun has assumed to role of Team Leader, and we’ve established roles for the agile software development part of the project. We also ordered and received the hardware we needed for the project.

For next week, we plan to spin up a rudimentary mobile application to start adding features and UI components. We will separate functionality into stories and assign developers to each, with daily stand-ups to report on our progress. In addition, we will start working with the hardware we received and decide on what is needed and will be used for this upcoming prototype.