Besty - Carmen, Leah, Yael, and Quai

[goaskcarmen]

No description provided.

[ghost]

staying organized:
we took a long time to plan at the beginning of the project and that helped us to build a solid foundation of being on the same page regarding the 'skeleton' of the project. along the way, frequent pull requests and merging kept us on the same page.

should have done differently:
it is not a team thing but more of a curriculum thing - it is hard to concentrate on new things taught while working on betsy. and the HW load was not respective of the project as well.

recommendation for C7:
look above...

• staff: please make sure there are always TA available to help during project time.

technical:
went well:
we managed to overcome git issues on our own successfully. feeling way more comfortable on that.
challenging:
keeping our energy levels high enough to keep functioning efficient;y during all project times.. breaks like comapny engagement times were helpful fir that purpose.

overall feeling:
teamwork - good.
personal achievements - I regret not owning the most challenging part of the project, which was the cart, but I did become more fond towards front end which was nice!

[goaskcarmen]

The Trello board helped us to stay organized and working together. Each card on the Trello board was color coded according to the controllers. Each team member worked on her own controllers to minimize conflict. We reviewed all pull requests together. At the beginning and the end of each day, we all did a pull request and merged, so that everyone was working on the same version.

At the end of the project, we were slacking on updating the Trello board. It did not have any adverse affect on this project, but it could for a bigger project, in my opinion.

Communication is the key for a successful project. All team members updated each other on what we were working on every few hours so that we stayed on the same page at all time. We also had our own retrospective at the end of each day.

The team worked together very well. Everyone was super supportive of each other. Everyone took ownership of their products.

I wish I could have done a lot more on this project.

[lbueing]

How did your team work together?

• What helped you stay organized and working together?
  We communicated quite a bit. It was helpful sitting in the same physical area so that if we had a quick question is was easy to get a response without having to seek someone out.
• What should you have done differently?
  We spent A LOT of time planning exactly how our project would look before beginning. Though this helped give a strong beginning direction, we still ended up doing about a dozen different migrations to account for mistakes we had made or things we didn't think of at the beginning.
• What would you recommend to C7?
  Daily 10-15 minute 'emotional check-in'. This seriously helped. It allowed us to stay positive and voice any frustrations we were having either with the project our how the group dynamic was going. It also gave us the opportunity to support each other which overall led to a better experience.

Technically?

• What went well?
  Merge conflicts were to be expected, but they were almost always minor. The way we divided the responsibilities worked very well for us. We each took a controller or two and owned it. There were crossovers of course, but during those moments we took time to pair program.
• What was the most challenging?
  Everything was so connected. Sometimes a small tweak would have unforeseen consequences. It was sometimes frustrating to know you hadn't changed the carts controller at all and yet the cart was no longer functioning as it should. It did however lead to a better understanding of how all the pieces fit together.

The overall feels??
I am pretty proud of our group. Though Betsy was a difficult project, we learned a lot about solving our own problems and we accomplished so much more than I thought we would. Luckily this is week 2, because I was not feeling as chipper at the end of week 1. I am really happy with what we've accomplished, and it makes me more hopeful about actually being ready for the capstone, internship, and post-ada career. :)

[Qlwentt]

What helped us to stay organized and work together

• constant communication was key to our success. We did code reviews very often and we know what each other was working on.
• one thing we could of done better to work together well was that we often picked different ways of doing things and made our program inconsistent. That increased the possibility of someone's code breaking someone else's. For example, exclusively using resources for the routes could have prevented some broken links because it is always clear what the route is.
  -Recommendations for C7: try to have fun with it

-My group members did a great job on their work. They learned advanced features/things we didn't learn about in class. Yael grappled with Foundation, put some javascript in our project for the dropdown, and partially rendered the reviews beautifully. Carmen was a champ when I said that we should use a HABTM relationship for products and categories even when that meant she had to learn how to deal with a new kind of relationship that is frankly harder to work with than HMT (and was probably a bad idea). Finally Leah implemented the most challenging part of this project---the cart and she handled it with excellence. I'm impressed with their work and appreciate everything they've done on this project.

-the sheer amount of work was hard on this project. It was hard to get everything right because there was so much to do. I really which I had time to work on more comprehensive permissions, testing, and validations.

I feel ok about the project, but I wish I could have done more.