Workshop 1 Scrum Report

[srujanr40]

1. What did you work on this past iteration (2 weeks)?
2. What were any major issues/challenges you ran into?
3. What do you plan to work on for this coming iteration (2 weeks)?

[srujanr40]

Srujan Rao k1w2b

1. Collaborated with the team to figure out a project idea, and break it down into goals of varying difficulties.
2. Reaching a consensus on how we would handle log ins and user authentication, given the pros and cons of each approach (eg. unique plaintext, SMS/Email authentication, id/password).
3. • Create the initial project file structure that future code can be pushed into
   • Create and style the join session page
   • Possibly start work on the data structure for future back-end work

[edvinkeskin]

Scrup Report for Edvin Keskin

1. Come up with a project idea, breakdown the project into parts and add features to the pre-existing idea. Distribute duties

2. Coming up with a team/project name. Deciding on which project idea to go with, considering which technologies or approaches to use for features such as login or location

3. • Create, style and add fuctionality to the list of sessions page
   • Back-end work?

[ksridar]

Krish Sridar t7w2b

1. Discussed with team members on how to approach the project, brainstorm ideas, and suggest possible implementations
2. Deciding on the features and how in-depth we need to go to achieve a good balance of frontend and backend
3. • Iterate on the lo-fi prototypes and see what makes the most sense user experience wise
   • Implement the dashboard page (layout, styling, routes) to achieve the minimal requirements
   • Research tools, frameworks and libraries that can be used to structure the project

[Taqdeer]

Taqdeer Grewal e2k1l

1. I took initiative to set up the team meeting to submit the project report. In the meeting, pitched some ideas like - going with the Netflix metaphor for frontend design, including filter pills and including email verification along with SMS to keep it doable. Also, asked questions about my other team members' ideas for more clarity.

2. I had a hard time adjusting my schedule to have collaboration with my team (should give my availability way ahead of time). Also had some communication gap while coming up with lo-fi prototypes.

3. For next two weeks, I plan on learning react, creating some dummy data, implementing the frontend part of Dashboard component using react-redux and will do code-reviews of my fellow team members.

[rkelly123]

Rory Kelly v7y2b

1. During this past iteration, I helped my team brainstorm ideas and land on a topic that seems interesting to all of us. I explored how some of our ideas might be implemented, and discussed those possibilities with my team.
2. There were no major challenges with this iteration, however, we did have some difficulty solidifying certain parts of our implementation plan. In the end, though, all it took was some discussion and we were able to make the necessary decisions in order to finish forming our ideas.
3. For the next 2 weeks, I plan on further exploring how to use react/reduct in order to build a responsive webpage, and begin implementing some of the most basic react components that we will need such as those relating to the manual create session and join session workflows. Specifically, as of right now, the plan is for me to take on the joined sessions landing page and the components that relate to that. I also foresee further discussions with my team about style and functional choices, as well as potentially some pair programming in order to begin fleding out some of the front-end to have something to build off of in the future. Additionally, I will carry out any code reviews that are expected of me.