Skip to main content

Remote Control Design Challenge Reflection


During this Monday's class we were tasked with coming up with a design for a universal remote control, that would be suitable for ages between 18 and 80. We decided to come up with a remote that was similar to what already exists since everyone knows how a TV remote controller works and what the basic functions should be. And since we had to make it suitable for people with bad eyesight or who may not be able to adapt easily to a change in the layout we made the main functionality of having numbers and two separate buttons for changing the channel and changing the volume a prominent feature on the remote. Thus people who are used to what already exists should be comfortable with using this remote.

For technologically inclined users, we accommodate them by providing them with a context-sensitive slide-out touchscreen that provides the user with the additional functionality such as a keyboard and trackpad if they want to use their SmartTV to browse the internet. As well as this due to the inconvenience of having no batteries available when the batteries in the remote die
out, we decided to include a charging option so that the remote can be charged using a regular smartphone charger.

Comments

Popular posts from this blog

Sprint 2 - Reflection

We started this sprint off with sprint planning sessions. We had two planning meetings. One occurring on Monday directly after our Advanced Professional Skills lecture and another meeting taking place after our lectures had ended Tuesday afternoon. Organizationally we made one change in the way we segmented our communication. We decided that instead of having multiple channels on Slack for the various aspects of our work that we would have a single channel for each week of the term. And thus for this sprint, we relegated all our communication to the new week3   channel on Slack. Our first planning meeting was short due to the lecture slides not being on available on Blackboard making it difficult for us to work out which tasks we had to do. However, we could decide on who could write this week's sprint retrospective blog. Also, we decided on a final name for our product. We all posted what we believed would be a good name for our product, into the week3 channel so th...

Sprint 4

This weeks sprint took place on the 2nd of October at 12:15. There were various items that need to be discussed and task that needed to be assigned. To start, we created a new channel in Slack for the week. We then discussed each task individually. Through discussion we were able to assign tasks that suited each individuals attributes. There was brief conflict as both Hasan and Joanna wanted to create the storyboard because they both enjoy working with design, in the end, we came to a compromise where Hasan would get this design task and Joanna would get the next. The other tasks were assigned with no issues. We discussed who we could contact in other to gauge the market. We decided to think individually on this task for the week and present our ideas during Monday's sprint. We decided this because we all initially had the same or very similar ideas such as surveys and emails to companies etc. We concluded that working individually on ideas for now, might lead to a more creativ...

Sprint 7

Sprint 7 took was divided up into 2 parts. Originally it took place on Monday 23rd Oct in The Hub where our team met up to discuss all the work we had to split up for the upcoming week. We have done the BMC the week beforehand so we were happy with this being a lighter week workload wise. We split up all the tasks we had to do and updated each other on what we've been working on so far so that we're all on the the same page when it came to things like the production price and where it came from and who we talked to about our product ThawSafe amongst other things. We concluded our sprint and went about our week knowing that we all were aware of what we had to do individually and what all our teammates were doing also.   Throughout the week we noticed other teams talking and working on their deliverables for the module that we haven't realized we had to do. It was a busy week full of lectures so none of us had much time to meet up and recheck if we had all tasks account...