Feedback in Scrum Methodology

Agile

Feedback in Scrum Methodology

Feedback in Scrum Methodology

Like any other Agile methodology, Scrum uses the feedback practice to improve the quality of its software products. In this article, we will tell you about the specific features and procedures of feedback in Scrum. But before doing that it is necessary to describe the methodology itself because it is impossible to understand the nature of Scrum feedback without knowing its basics.

Scrum is currently the most popular Agile software development methodology. Like many other Agile methods, it originated in the early 2000s. The popularity of this method is so wide that some developers even confuse Scrum with Agile, which is a wrong thing to do, as Agile is an umbrella term. Scrum is only one of the Agile methodologies. It shares all basic principles of Agile like strong customer involvement, strong communication inside of the teams, and iterative structure of projects.

Strong communication is required because Scrum teams are small. They do not include such roles as testers, project managers, and analysts, which are typical for the traditional software development methodology. A Scrum team usually has only three roles: the ScrumMaster, the Product Owner, and the team itself.

A ScrumMaster is not a formal leader or a project manager. He is only a coach that teaches the team to implement the most effective Scrum practices. A Product Owner is the customer or his direct representative in the Scrum team. He is the person responsible for gathering user stories and prioritizing them in the product backlog. He also estimates the intermediate products after each iterative cycle.

The iterative cycles in Scrum are called sprints. Every sprint begins with the formulation of a sprint backlog. It is formulated at the sprint planning meeting. After the backlog is formulated, the Scrum team begins its work on a certain sprint. When the intermediate product is ready to delivery, the team members conduct a Sprint review. After the customer estimates the product they conduct a sprint retrospective to define what went well and what went wrong during the sprint.

Now, when we know what Scrum is and understand its nature, we can start our talk about feedback in Scrum methodology. Generally, there are three types of feedback in Scrum: team feedback, customer feedback, and user feedback.

  • The team feedback is the opinion of the developers on their product. Usually, they discuss it at special meetings called sprint reviews. At these meetings each team member can say his opinion on the advantages and disadvantages of the sprint product. If the developers detect some defects in the product’s functionality during the sprint review, they have to fix them.
  • The customer feedback usually takes place after the end of each sprint. The Product Owner estimates the intermediate product and gives his feedback to the developers. If he is not satisfied, they must continue their work on the product’s functionality.
  • The user feedback is usually received during the user acceptance tests when the final users can estimate the product and say about its disadvantages.

No Comments

Leave a Comment

Please be polite. We appreciate that.
Your email address will not be published and required fields are marked


Share via
Send this to a friend