My capstone project AudIQ was about to suffer from a small scope creep, which is when the changes, continuous or uncontrolled growth in a project’s scope. Before the development of the mobile application, we had laid out our customer need for the project and then prioritize the customer need which is most important to accomplish. For instance, one of the scopes for the mobile application was the game script or storyboard of the game. This scope was needed to be finalized before the GUI programmer worked on the game and before the back-end database programmer created the structured relational database. The first semester of the capstone we created a storyboard and how the levels would increase. However, we realized the game did not need game levels. Thus, the way we handled this change was by only changing the organization of the database because it was not fully created. At the time was only a very small prototype. However, if the entire database structure was created for the old version, there would be serious changes. One way to fix this would be having two people work on the database instead of one. This situation to an extent could be avoided if our team planned the storyboard of the game well. However, certain situations cannot be predicted until the team started to work on the project. Thus, changes to project scope can effective a project is delayed.