The initial goal of the Scrum team project was to apply acquired knowledge about the agile approach and Scrum framework. Thus, we followed Scrum principles. Three members of the team and I defined project requirements, created a risk register, and milestones, planned sprints, created product and sprint logs, and used various collaboration tools for design, development, and agile management.

During this project, the team created a Portfolio Helper website which provided information about how to compose and build an e-portfolio. The purpose of the Portfolio Helper project was to help users find current, complete, and practical information on how to create an e-portfolio to get better opportunities for hiring for the desired position. The goal of the project was to create a helpful tool and environment where users can learn how to build an e-portfolio from the beginning and share their tips and experience with other users.

A Scrum team included three students and me. Our group of collaborators worked toward completing the project and delivering a product. During the work, the team used a Scrum framework for the project management process. The Scrum team worked on different segments of the project at the same time. The Scrum team valued self-organizing collaboration, feedback pathways, and sustainability in project development.

As a team member, I was accountable for communication, user flow, UI design and mockups, task assigning, backlog management, content editing, and single webpage development. I used Figma, Smartsheet, GitLab, and Google Docs to perform my responsibilities. Although I performed more roles as a Product Owner for this project, all members of the team followed Scrum principles. We did not have a team member with a distinct role as a Scrum Master. Some of the roles of a Scrum Master were performed by me and one other team member, such as assuring that the team follows Scrum principles. However, it is not a good practice to overlap the roles of a Product Owner and Scrum Master.

For website development, we used React and Visual Studio Code. Also, we used GitLab as a repository, where each member of the team made contributions by merging changes. We were communicating with team members using Discord while updating the repository.

During the process, we followed Scrum framework and Scrum values according to the Scrum Guide, such as Commitment, Focus, Openness, Respect, and Courage. We were able to create a friendly environment for teamwork. Our team was committed to achieving the goal and supporting each other. We valued communication as an important instrument for a successful project. Each team member felt free to ask any questions and discuss their roadblocks.

Our team did not experience Scrum failures because we set a strong base for our work. Thus, we set good communication, had a planning strategy, creating a risk register and backup plans. we experienced some technical issues, but the solution was found quickly by team discussion or following response in the risk register.

The Scrum team project was successful. We met all project requirements and due dates. We produced a potentially shippable product at the end of each Sprint.