codepathreview
commented
10 years ago @shawnyapa, @sushant2603, @pmalviya - Nice work creating tasks for sprint 1 :+1: . The goal of this sprint is to have the basic screens and workflows ready as much as possible. A few notes
- Tasks are well defined and seem achievable in the given timeframe, it looks like a lot of work but will be great if you guys can pull it off
- Good work dividing tasks among team members. This is critical in working as a team and also gives equal learning opportunity to everyone involved
- Nice way of splitting a parent task into a number of smaller subtasks - provides a better picture of the progress on the issue
- Nice work creating and distributing tasks to create database schema and models. Checked out the Ninjamock wireframes and look good.
- Consider creating a project wiki so you can have a thorough documentation of all design decisions made during the project. You have a good start on this by listing down required and advanced features on ReadMe.
- Depending on the strategy your group has come up with, consider creating regular pull requests to sync up your code to avoid having multiple errors at the end.
- Consider creating tasks to QA the app a few times to check the basic flow. Integration testing will especially be important for this project since each team member is working on a separate module. The best part is seeing it all come together into a polished app.
Consider incorporating as many screens as possible in this sprint so you can have enough time to add UI polish and advanced features later on. It is those little extra things you do that make everything feel more polished and desirable to use. Look forward to what you all come up with.
Taste Buds -> Milestone Sprint 1 with Tasks, Date, and Assignment Completed - Please Review
Note: We assigned all Project Activities and Fragments to Sprint 1. This might be too aggressive. Advice and Feedback appreciated. @nesquena @thecodepath @codepathreview @pmalviya @sushant2603 @shawnyapa