Elvin Gonzalez1) Describe the agile Scrum method. Describe all roles, e.g. Product Owner, Scrum Master, etc. (2 pages) Scrum is basically a framework for agile development. Scrum is a process used most of the time during complex software development projects. It's also a simple but effective way to manage work. The strategy in Scrum is to divide members into a team and have them work together to achieve a common goal or project. Scrum causes communication between team members. This communication is critical to the success of the project. The Scrum approach is quite flexible. This allows the project to adapt whenever a new situation arises. This aspect of Scrum is quite important as all projects undergo changes during its scope. The ability to adapt allows your project to stay relevant. This is especially essential in the rapidly evolving world of technology and software. Scrum takes an empirical approach. This means there is an understanding that all projects will face unexpected challenges. Scrum maximizes its capabilities to deliver and respond to these changes. Scrum is a simple concept that tackles difficult tasks. The core of the scrum can be divided into 3 main roles; product owners, development teams and Scrum masters. The product owner is usually a key stakeholder in the project. The project owner has a very essential role. The product owner must have a vision of what they are trying to build. This means that they will be the ones driving the direction of the project. The Product Owner must also be able to communicate effectively with his team to convey the vision of the project. This is a very important task because the development team needs a… medium of paper… test box. With black box testing every time someone commits their project, I would test it to see what's wrong. This would give me an idea of ​​what needs to be worked on. I would use it to write a long list of things that still need to be completed so that my group members can tackle any issues on the list. There have been many cases where team members have changed the code assigned by other members. However, we have never deleted their code; we simply post them in a comment block. Whenever someone committed their code, we messaged each other asking for feedback. Peer review often helped us find a solution together. The fact that we were communicating for review meant that we also discussed all of our ideas for the group project. All in all, I would say that code review is an essential part of creating quality code.