At this point of the capstone course, there remains approximately three weeks left. I found that the process of implementing my group’s capstone project (i.e. Crowd-Sourced Travel Planner) went smoothly and efficiently. A major contributor to this outcome comes from selecting a group prior to the course start, along with clearly defined expectations from the course.

During this last sprint, I focused on addressing minor web app behavior issues, such as pagination not being persistent in pages with multiple lists. For example, the profile page contains a user’s created trips and experiences. Assuming a user has more than 3 trips and experiences, if a user navigates to another trips’ pagination sequence, the experiences’ pagination resets to the first page, and vice versa. These types of QOL improvements are expected to be emphasized in the following weeks.

When developing the web app, separating features into individual branches and coordinating when to push features helped significantly in preventing the occurrence of any merge conflicts. As it pertains to the project’s functionality, most of, if not all of, the core features have been implemented, with bug fixes and potential stretch goals planned for the final stretch of the course.