Ride Share - Sprint 2

Over the course of this sprint, our team made a lot of headway establishing a fleshed out ASP.NET code base to work with and build upon in moving on to future sprints. We decided upon and implemented our database to be used by our application, including stored procedures to both write information to, and read from the database. We've also built out all the necessary user models for the application. Deciding on the best method to handle user login and registration, and tracking of user locations, we ended up choosing to integrate Google API which has been largely completed and should be easy to use in future sprints.

As for myself, I implemented the basic views for the application, including links and early design. These will, however, be revised and reworked in future sprints to better match client expectations. I actually found myself short of work during the sprint because of this, and so by request of the group moved my attentions to researching SignalR, which will be used for implementing peer-to-peer in-app communication in future sprints.

Looking back on this sprint as a whole there were a lot of problems with our team that must, and will, be addressed in the future, but there were at least some positives. Despite much of the application requiring to be reworked at this point in time, the vast majority of the code and work we've put in thus far is still very usable and should hopefully make the transition in sprint 3 far less painful. As for those problems, I've let this sprint be a lesson to me from here on out to always keep my client in mind whenever our group is making any decisions. Our group displayed poor communication this sprint, with nearly half of us being absent during our initial meeting with our client, then those who were there failing to properly communicate to those who weren't the client's agreed-upon expectations. It was also clear that none of the members in our team were interested in conflict, which resulted in lop-sided decision making that quickly led the group off track.

To sum up some lessons I've learned here:

• Always make sure every team member understands the team's goals from the beginning
• Never be afraid of conflict or disagreements, especially if the team is slowly derailing
• Never forget the expectations of the client
• Always keep the client in mind when making decisions
• The client is always right!
• Client!