In my role as scrum master, I took charge of organizing and ensuring the productivity of the team. To achieve this, I maintained a scrum board throughout duration of the period that we worked together.
Additionally, I did my best to remind my teammates and keep them up to date with our progress, and made sure that everyone was on the same page.
Here are some of my accomplishments and contributions to the overall team project.
Developed the Inventory management system from scratch
Connected backend database to frontend code
Created a database model and a fully functioning SQLite table for the backend
Contributed to the creation of a deploy guide for me and my fellow APCSP peers to use for AWS deployment
Created API endpoints for the backend
Helped deploy our backend through AWS and Docker
Utilized GET and POST methods to receive data from backend and input into database
Technical Achievements (Backend Focused)
Prior to this trimester, I only had basic knowledge of the SQLAlchemy Database Library and had not worked with it before. However, after utilizing it extensively during my project, I became proficient in using it for tasks like creating, reading, updating, and deleting entries dynamically in a database table. Although I initially faced challenges in programming the GET and POST requests for my feature, I am grateful for these setbacks as they forced me to gain a deeper understanding of the library and its functionalities. Now, I can successfully implement it into my feature and any future projects, allowing for the creation of a dynamically updating database on the frontend through the use of GET and POST requests.
Another one of my significant accomplishments in this project was acquiring proficiency in utilizing JavaScript and Fetch. Before starting the project, I had a basic understanding of frontend and backend development but was unfamiliar with how to link them to create a well-functioning project. By learning more about JavaScript, Fetch, and their purpose, I was able to connect the frontend and backend Flask server in my feature. This knowledge was critical in programming and allowed me to complete the final touches of my feature. As a result, I am now able to apply this valuable knowledge in future full-stack projects.
Personal Achievements
As I embarked on this project, I quickly realized that it was going to be a challenge. However, breaking down the project into smaller components and creating a list of tasks helped me to gain a better understanding of the requirements. I learned the importance of taking one step at a time and making consistent progress towards my goals. With dedication and persistent effort, I was able to overcome the obstacles that came my way and keep moving forward. This project taught me the importance of patience, discipline, and perseverance in achieving success. I now understand that hard work and a commitment to excellence can go a long way in achieving my goals.
Since I encountered various challenges that required me to think critically and problem solve, I realized that asking better questions was key to finding solutions to my problems. Instead of simply giving up when I hit a roadblock, I learned to approach the problem from different angles and think creatively about possible solutions. By breaking down the problem into smaller components and asking targeted questions, I was able to identify the root cause and find ways to overcome it. Problem solving became a central part of my approach to completing the project, and it helped me to stay motivated and focused on my goals. Through this experience, I learned that developing strong problem solving skills is a crucial component of achieving success in any project or endeavor.
Github Analytics
**Note: Most of my progression was made locally**
Here are my GitHub stats for our frontend site:
Here are my GitHub stats regarding my backend contribution:
For the next project cycle, I aim to improve our workflow by ensuring that more work is done at the beginning when the project is assigned. This trimester, our group left a lot of work until the deadline, which caused stress, especially when debugging multiple errors. By working consistently from the start, we can deliver a higher quality product with less stress. Additionally, I want to prioritize improving the frontend design next time. This trimester, we focused more on the backend and SQL aspects, so we were unable to dedicate much time to making the site look professional and visually appealing. Overall, I believe that we did well, and there are many lessons we can take away for the next PBL cycle.
Night at the Museum:
[x] Here is my N@TM blog
[x] Attendance & Presentation to Teacher
Crossover Grading
My Accomplishments:
Here are some of my accomplishments and contributions to the overall team project.
Technical Achievements (Backend Focused)
Prior to this trimester, I only had basic knowledge of the SQLAlchemy Database Library and had not worked with it before. However, after utilizing it extensively during my project, I became proficient in using it for tasks like creating, reading, updating, and deleting entries dynamically in a database table. Although I initially faced challenges in programming the GET and POST requests for my feature, I am grateful for these setbacks as they forced me to gain a deeper understanding of the library and its functionalities. Now, I can successfully implement it into my feature and any future projects, allowing for the creation of a dynamically updating database on the frontend through the use of GET and POST requests.
Another one of my significant accomplishments in this project was acquiring proficiency in utilizing JavaScript and Fetch. Before starting the project, I had a basic understanding of frontend and backend development but was unfamiliar with how to link them to create a well-functioning project. By learning more about JavaScript, Fetch, and their purpose, I was able to connect the frontend and backend Flask server in my feature. This knowledge was critical in programming and allowed me to complete the final touches of my feature. As a result, I am now able to apply this valuable knowledge in future full-stack projects.
Personal Achievements
As I embarked on this project, I quickly realized that it was going to be a challenge. However, breaking down the project into smaller components and creating a list of tasks helped me to gain a better understanding of the requirements. I learned the importance of taking one step at a time and making consistent progress towards my goals. With dedication and persistent effort, I was able to overcome the obstacles that came my way and keep moving forward. This project taught me the importance of patience, discipline, and perseverance in achieving success. I now understand that hard work and a commitment to excellence can go a long way in achieving my goals.
Since I encountered various challenges that required me to think critically and problem solve, I realized that asking better questions was key to finding solutions to my problems. Instead of simply giving up when I hit a roadblock, I learned to approach the problem from different angles and think creatively about possible solutions. By breaking down the problem into smaller components and asking targeted questions, I was able to identify the root cause and find ways to overcome it. Problem solving became a central part of my approach to completing the project, and it helped me to stay motivated and focused on my goals. Through this experience, I learned that developing strong problem solving skills is a crucial component of achieving success in any project or endeavor.
Github Analytics
**Note: Most of my progression was made locally**
Here are my GitHub stats for our frontend site:
Here are my GitHub stats regarding my backend contribution:
Runtime Link
Backend Model
Backend API
What I would do differently...
For the next project cycle, I aim to improve our workflow by ensuring that more work is done at the beginning when the project is assigned. This trimester, our group left a lot of work until the deadline, which caused stress, especially when debugging multiple errors. By working consistently from the start, we can deliver a higher quality product with less stress. Additionally, I want to prioritize improving the frontend design next time. This trimester, we focused more on the backend and SQL aspects, so we were unable to dedicate much time to making the site look professional and visually appealing. Overall, I believe that we did well, and there are many lessons we can take away for the next PBL cycle.