Brainstorming Session

Hello! Last week, we created our Product Design Specifications document which helped us defined the wants and needs of our sponsors. From this document, we were able to define which aspects of the project held priority and which requirements interlaced with each other.

This week, we presented our team name and logo to our class and received feedback that we will be taking into consideration. In addition, we had an in-class brainstorming session in which each of us wrote down an aspect of our project and direct messaged it to another team member. From there, the next team member built of this idea and passed it onto the next person. This continued until the original team member received their original idea back to them with additional ideas built on top of it. This was a great exercise for us to delve into components of the project and for everyone to contribute their ideas.

During our meeting with our liaison, we also presented our logo to him and received approval for the design. We also discussed the roles of the project that each of us would be interested in tackling to help divide the workload and parallelize the software development cycle. From these interests, we are going to do additional research on each of the topics and understand more of the potential different tech stacks.

Wireframe for lazy loading

During our coach meeting, we discussed each domain of our projects and broke them down into tasks that we placed into a Gantt chart. This will help us by telling us which tasks have been started, the progress of each task and if they have been completed. We also created the initial draft of low-fidelity wireframes for our project and presented those to Dr. Silva.

Next week, we plan on working on researching more on each of the roles we have been assigned and start working towards the tasks listed in our Gantt chart.

Leave a Reply

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