This is the part 1 of the first update regarding the Travel Buddy mobile applications development. The reason why I have split into to parts is because as mentioned previously I will also discuss about the PI planning I did for my self. I will try to be on top of the sprints and give updates 1 or 2 times through the sprint, but will always give 1 update at the end of the sprint. During the end of the sprint update I will also talk about a reflection to document the challenges I went through during debugging and implemetation.
In order to begin the project development I have broken down into more digestable of different phases. Within the phases it is brokendown further into features and finally within the feature I have brokendown into the possible tasks which are required to be completed. Within this planning I have began to test with something new categorising each feature to see it imporantance [Must have, Should have, Could have, Nice to have, Will not have]. The Importance catergory was a difficult to apply to the features as I was treating my self as the user while also having the developers mindset. As there were some features I was maybe overthinking on whether if it was required or not.
Based on the size on my project I decided to break it down into 4 different phases. In phase 1 it includes the core development features such as the login, sign up and chatting with the chat bot capability. While implementing the . Phase 2 contains the development of the trip planning feature, where the user can edit the daily itinerary for the trip with budgetting tracking. Phase 3 is compromised of the implementation of extracting the chat and auto populating the itinerary for the user based on the chat they are satisfied with. Last and final phase 4 contains testing, especially testing for the edge cases.
Through the project I will utilize the AI as my co-developer on this application. As felt like after testing before I start, when consulting with AI it always ended up agreeing with me which is not good. Especially when I point out maybe its better to do it this way, and it proceeds to apologize and implement in a way I suggest. Which can end up being the wrong way. I will treat and have trated it as a co-developer/used for brainstorming and attention to detail checking.