In interviews, you'll be asked about how you approach working in projects, and being able to describe how you utilize agile processes is a great way to help you stand out as a junior developer candidate. This reflection is meant to help you develop this skill.
With that in mind, please answer the following questions in your own gist about your group project:
What have you learned about the use of agile vs. waterfall in software projects?
I guess we used something looks like agile development in our project. Because we did our project stage by stage, when every stage included work, test and deploy and new functionality was added in the start of every stage.
How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)?
We use github project during all working time, and tried to use ToDo board (Trello).
What role did you take on in the project?
I was as one of team members, I took some tasks for working separately and made it done. Also when we work together I suggested some ideas and explain something if it was necessary.
What changes would you make to your approach in future team projects?
I would make group work more organized and add more discusses and retros of work.
How does retro function in a team project?
We didn't have enough retros while working on project. All time retro was a small reports about what has been done.
In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
Unfortunately, our team communication and feedbacks were very poor. We don't discuss how somebody worked, what we got from our work or others.
How would you describe your ability to communicate feedback? How has this experience affected your communication skills? How do you want to improve in your ability to communicate feedback?
I can say that I feel discomfort when I want to give some feedback to other. If it's unnecessary to give detailed feedback, I can limit it only short appreciation, because It's hard to estimate other's work. Step by step I'll learn how to give feedbacks and how to do it more professional.
I appreciate the reflections here, and I would encourage you to continue to reflect in detail on the processes and lessons learned you see in each project.