Team Charter

Definition of Done A task is considered "done" has been completed and reviewed and is of adequate quality and no further changes need to be made for it to work with the current codebase. A team member is considered "done" with their part of a task when they have completed all requirements of a task and have ensured that the changes work with the current codebase and consist of quality code.

The project is done when the user can create, see, update, and delete a task. The user will also be able to log the completion of a task in the past, present, and future. The total point counter is accurate and changes with completing a task or purchasing a reward from the shop. The user can purchase, create, see, update, and delete a reward. The UI looks presentable All other aspects of the project work as intended All code is well written with sufficient comments The project has been end-to-end tested, including unit tests Up to date documentation All code is committed and pushed

Working Agreement We work best together when we communicate via Discord and there will be an acceptable response time of 5 hours, when we openly communicate with other members of the team valuing different perspectives, when everyone is accountable for their tasks and deadlines as well as their mistakes, when we allocate tasks depending on others tasks and workloads when we recognize that change is inevitable and we must learn to be patient and adapt adequately when we value everyone's time and commitment to their work. We also work well together when we meet once a week outside the class when individuals are free to work on the app. Calendar Each team member will devote at least 2 hours to the project every week outside lab meetings. Every two weeks the team agrees to review tasks that have been considered done due to the definition of done in the Team Charter. In addition, we will meet one a week outside the class to work on the development of the app. Sprint #1 Retrospective Our team gets a pretty sufficient amount of quality work completed and for the most part we tend to work well together and communicate efficiently. The first change we are going to implement is meeting up after our lab on Fridays to work on the project to keep us on track and so we can communicate face-to-face before we leave for the weekend. The second change we are implementing is switching from using Flutter to React Native so it's easier for us to use an emulator. SIGNED BY: Vruj Patel, Evan Toomey, Leo Thomas Sprint #2 Retrospective Our team got a very god amount of quality work completed for this sprint and we worked well amongst each other. Considering how we had to overcome the learning curve in React Native and being able to create or app the progress we made within this sprint is very satisfactory. The changes we are going to implement going forward is to meet us right after the labs to continue working on the app since it proved to be a productive method for us to continue the productivity streak after the lab when we tried once during this sprint. In addition, we have decided to get together every week after the start of each sprint to figure out what features and code we can improve to make our app efficient. SIGNED BY: Vruj Patel, Leo Thomas, Taqi Tahmid, Evan Toomey Sprint #3 (closed) Retrospective Our team did well in dedicating time outside the lab to catch up on tasks in a productive manner. In addition we did well in communicating with each other via discord to manage what tasks needed to be completed priority wise and in helping each other resolve issues. We also did well in consulting with others about the UI interfaces for certain tasks to get a different perspective. After we established that we have been working more efficiently this sprint we came to a consensus that we don't require any changes at the moment. Team Goal: To Get the functionality of the App to finish so that we can start getting closer to what we had envisioned for this term from CI 102. SIGNED BY: Vruj Patel, Leo Thomas, Evan Toomey, Sprint #4 Retrospective Our team did good in making progress and actually dedicating time outside the lab to work on their individual tasks. In addition, we believe that we did good in asking for help from others when we were struggling so that tasks could be completed faster. After we decided that we have been doing a good job on completing tasks and relying on others, we decided that we need to meet once a week in person to making debugging and relying on others easier. Team Goal: To finish up the essentials of the app and start on the back-end development for user profile and login. SIGNED BY: Vruj Patel, Taqi Tahmid, Leo Thomas, Evan Toomey (Planning CI103)-----------------------------------------------------------------------------------

• Our group got together and had a meeting with our scrum master for the day to get a better understanding of our plans for CI103. We first all consecutively decided that we would continue with the development of our current app and didn't need to start over again. We came to a consensus that our app is at a stage where it is viable and can be modified to meet our vision of the app. In addition, it was decided that we would create new user stories since we got many good suggestions to help make the app user-friendly and interesting for the user. Since we want the users to be contempt with the app, we will add user stories related to their suggestions to meet their needs. When it comes to the prioritization of the user stories, we decided to prioritize some of the user stories that were intended for ci102 and save the new user stories for later so that we can get the app fully functional before improving upon the concept of the app with the new user stories. The user stories that we believe are reasonable to complete in this sprint are allowing to user to create tasks and rewards and being able to assign points to each, creating a streak/calendar to motivate further continuation, dark and light theme mode, and animations. Signed By: Taqi Tahmid, Leo Thomas, Vruj Patel, Evan Toomey