Since our capstone project is pretty much completely finished, we
had the honor of getting to go into Ombitron and presenting our product to
them. We got to explain our process, design decisions, and how we worked as a
team. This part of the milestone was very important for having us practice our
presenting skills to an audience. From this presentation, we now have a clearer
idea about how we want to present our project at the capstone event.
The second part of this deliverable had to do with receiving final
feedback on our project based off of the user testing done by Ombitron since we
make corrections based off of the last bit of user feedback we received.
Unfortunately, Paul was very brief with us about giving meaningful feedback.
Our team came up with a long list of questions to ask Paul, but his response
only answered a few of the questions that he had. I can only imagine he already
has a lot on his plate though being a CEO of the company. Regardless, Paul did
let us know that he gave multiple demos of the dashboard to clients. They
didn't have anything negative to say about the dashboard, and found it easy to
use. They were able to tell what the graphs were and found the data valuable
and easy to understand. Paul also agreed with us about changing the colors of
one of the icons and gave us more information about how the hardware measures
humidity.
This part of the deliverable helps us resolve any worries we had
about making any last minute changes. Perhaps our process for obtaining
information from Paul was flawed since we contacted him over email. we could
have gotten more useful feedback if we chose a different way to contact him
about feedback. Nevertheless, this part of the deliverable helps our team
finalize our capstone project and allows us to solely focus on the poster from
here on out.
Below is a screenshot of the email we sent Paul and the feedback
we received.
No comments:
Post a Comment