Sprint 2 Retrospective

 Links to evidence of activity on GitLab.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/generatewcfbreportfrontend


I created a new generate WCFB report frontend which I used the sample frontend example from the professor. I have already had a basic model for the Frontend. I need to do more to connect the backend API, which can let customers download the report for the inventory.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/23


I designed the API for backend endpoints.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/34


I met with Marcos and Matt and talked about the difference between each group's FrontEnd design. For the next sprint, we will be having more meetings to help each other out on the API.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/35


I looked for WSU visual standards to use for the frontends.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/61


As a team, we created a Docker_compose file for the Integration of all systems.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/67


I implemented FrontEnd for Reporting with the most recent version


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/55


I am stilling mak OpenAPI.yaml fileReflection on what worked well?


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/71


As a team, we are looking at the new architecture and plan accordingly.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/66


As a team, we are looking over TheasPantryReport.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/20


I am researching Kubernetes with Migena.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/22


We are reviewing Scrum issue boards


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/12


We are reviewing LibreFoodPantry Architecture and technologies used.


https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/community/-/issues/58


I am creating a simple frontend to test keycloack with Migena.



Reflection on what worked well?


In terms of what worked well, team members are working together more efficiently to complete the project plan through the first phase of working together than ever before. After a teamwork period, we have a deeper understanding of our mission goals and become more accustomed to each other's habits. There will be a relaxed working atmosphere, and the chemistry between the groups will encourage each other to move the project forward.


Reflection on what didn't work well?

As for why it didn't work out, there was some confusion about the final product as to the project's future goals. When faced with unknown challenges, we are still a little confused. As we communicated with the professor, we had some clear goals. Because the front end and the back end are related, taking charge of every task affects productivity. So we have overlapping project leaders working together to get the job done, which improves efficiency. The mission was complex and challenging, but we encouraged each other through the ZOOM meetings after class.


Reflection on what changes could be made to improve as a team?

As a team with cooperation, smooth communication, and tacit understanding among team members are the basis and key to improving our team's cooperation level. We would discuss the project after class and give some constructive suggestions about each other's tasks. Good communication makes our team have chemistry. Through communication and cooperation, we have a thorough understanding of the team members' tasks. Each knew the other's project progress would be conducive to the overall advancement of the project. When a team member encounters a bottleneck in a task, we will appropriately slow down the overall progress and communicate with him to buffer his time to complete and push forward the overall task progress.


Reflection on what changes could be made to improve as an individual?

As an individual, I need to improve my understanding of the Frontend more quickly to help my team better connect Frontend and backend. I need to arrange my group tasks more reasonably to help promote the whole group project's completion. Besides, I also need to make clear my work objectives, continue to follow up on the team's project, and make my part and the whole develop simultaneously. 

Comments

Post a Comment

Popular posts from this blog

Breakable Toys

 We can all benefit from writing random "toy" programs to push ourselves to the limit by setting artificial limits. -- Donald Knuth, The Art of Computer Programming If you can learn as much from failure as you can from success, you need a relatively private space to look for the loss. In balling acrobatics, a performer who tosses three balls will never progress if he has never tossed five. Those who spend hours picking dropped balls until their back hurts eventually get good at it. The same lesson applies to software, where software workers often need to step out of their comfort zone to try something they're not good at it. It is by taking bold chances again and again that you improve your skills, that you learn and grow from failure after failure. Just as a three-ball-tossing performer does not throw five balls in a formal performance, software developers often make mistakes in new areas. Software developers also need a safe place to make mistakes. It's terrible not
Read more

What is Rest API

  API is short for Application Programming Interface (API), which describes a class library's characteristics or how to use it. Your personal library may contain "API documentation" of available functionality. A REST API in API Gateway is a collection of resources and methods integrated with back-end HTTP endpoints, Lambda functions, or other AWS services. You can use API Gateway features to help you with all aspects of the API lifecycle, from creation through monitoring your production APIs. API Gateway REST APIs use a request/response model where a client sends a request to a service and responds back synchronously. This kind of model is suitable for many different kinds of applications that depend on synchronous communication. When many people refer to API documentation these days, they often refer to an HTTP API that might share your application data over the web. For example, Twitter provides an API that allows users to request tweets in a specific format to easily i
Read more

Difference Between Black-Box, White-Box

 White-box or glass-box testing is testing from a program's source code without using the user interface. This type of testing needs to look at code syntax to find flaws or errors in the internal code in algorithms, overflows, paths, conditions, and so on, and then fix them. Black-box testing, or black-box testing, is rigorously tested by using the entire software or a software function without examining the source code of the program or having a clear understanding of how the program or the source code of a software function was designed. Testers understand how the software works by entering their data and seeing the results. Typically, testers run tests using not only input data that is guaranteed to give correct results but also input data that is challenging and may result in errors in order to understand how the software handles various types of data. The program under test is treated as a black box, without considering the internal structure and characteristics of the program
Read more