Scrum Essay

3134 Words7 Pages

Elvin Gonzalez 1) Describe the agile method Scrum. Describe all the roles, eg. Product owner, scrum master, etc. (2 pages) Scrum is basically a framework for agile development. Scrum is a process that is used most of the time during complex projects in software development. It is also a simple yet affective 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 provokes communication between the members of the teams. This communication is imperative to the success of the project. The Scrum approach is pretty flexible. This enables the project to be able to adapt whenever a new situation arises. This aspect of Scrum is pretty important since all projects undergo change during its scope. The ability to adapt allows for your project to stay relevant. This is especially essential in the fast moving world of technology and software. Scrum takes on an empirical approach. This means that there is an understanding that all projects will be faced with unpredicted challenges. Scrum maximizes on its abilities to deliver and respond to these changes. Scrum is a simple concept which tackles difficult tasks. The core of scrum can be divided into 3 primary 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 one who leads the projects direction. 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 to have an und... ... middle of paper ... ... box testing. With the black box testing every time somebody committed their project, I would test it out to see what’s wrong with it. This would give me an idea of what needs to be worked on. I would use this to write a big list of things that still need to be completed so it could allow my group members to tackle any of the problems on the list. There were many instances where team members changed the code committed by the other members. We never erased their code though; we simply put them into a block comment. Whenever somebody would commit their code, we would message each other asking for feedback. The peer review often helped us come up with solution together. The fact that we were communicating for the review meant that we also discussed all of our ideas for the group project. All in all I would say code review is an essential part of making quality code.

Open Document