-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scrum Report #1 (May 23, 2020) #1
Comments
For past iteration, I've come up with and refined our project idea, as well as doing rough sketch of UI and define the majority of project requirements. As this iteration is mainly brainstorming, the only challenge was to come up with a feasible idea that is interesting enough for us to commit to over the next 4 months - I went for personal app idea as I thought that'd require less data/user activities/interactions to make useful. For next iteration, I will be implementing expandable table component, as well as set-up the pages wireframe. |
In the past iteration I worked on revising and completing requirements of the project. The major issue I ran into was to fully visualize the project and make unanimous design decisions and deciding on the project topic that we can fully dedicated to. For the next iteration, I will be implementing map component as well as helping to style the main component. |
During the past iteration, worked on the project requirements document and brainstorming design. I ran into no major issues worth noting. In next iteration, I will be working on the main itinerary component for our app. I will also be going over some react-redux tutorials. |
In the past iteration, I worked on adding project requirements and researching potential project ideas. For the next week, I will be working on the notes/information component for our app. In the previous 2 weeks, the only significant difficulties I had were conceptualizing the selected project idea architecture when coming up with requirements. |
Josh (jrayo00) - e8m2b |
No description provided.
The text was updated successfully, but these errors were encountered: