Ride Share - Sprint 5

With our project turned around and an excellent presentation at the end of last sprint, the primary goal of the entire team this sprint was to manage risk and to prepare for a final presentation with the client, while freezing our product on the production server, only making minor polish and bug-fixing tweaks on the development server.
Our back end developer worried about all the final touches to the code itself, while our other member and I worked on preparing the presentation and final documentation. As far as the presentation goes, everything advanced smoothly with preparing that, however there were some concerns going into the deployment documentation to be passed off to the client, primarily in that deployment was previously handled by another team member. Between that and my own technical limitations on my end, it left me concerned. As I write this I am actually looking to finish up our deployment documentation, however, I am looking to communicate with our back end team member to help clear up any confusion in that regard.
These last couple of sprints have been a tight squeeze and this is no exception. And a lot of the issues we've had later on might not have been quite as bad if our team had not ran into so many issues early on. I know those kinds of things can not always be predicted and prevented, but this has shown me how important it is to make sure your development process has a stable foundation from the very beginning.

Ride Share - Sprint 4

The primary concern of our team this sprint was re-stabilizing our group. We had lost two team members, and it was clear that our goals for the rest of this project are, and have been, unrealistic. Over the course of this sprint, we spent time re-evaluating what we'd be able to accomplish for the rest of the course, and re-aligned our goals with the time frame. All extra and unnecessary features have been cut from our project, and we've boiled our goals down to those features that will be absolutely necessary to display primary functionality to the client. Advanced features such as live chat, and advanced route mapping have been scrapped for the time frame of this course, and focus has shifted over to correcting and improving data entry into the database by users, how that information is displayed, and overall user-interface.

As for myself, aside from aiding in the group re-alignment, I've been tasked still with front-end development, and have worked on implementing some neater, more user friendly controls for the pages we will be presenting, replacing basic toggle controls, so that the client will be able to see a more polished overall design for our next showing.

I think a big issue with this sprint specifically, is that progress was heavily stunted due to mistakes made earlier in the development of our project. Our scope had fallen far out of hand, leaving us with a project that needed some serious re-focusing before we could even hope to be prepared for out client. That being said, now that we've taken the time to simplify and re-focus, everyone is more clear on what needs to be accomplished, and I am feeling more confident moving forward.