Feeback

Feedback

In an agile project the team relies on real-time feedback to keep the program on track. As feedback rolls in, the team uses the feedback to respond to changes. If the product owner thinks that the project requirements are not being met, or if the scrum master sees anything that he or she thinks needs to be changed, that feedback is there for the developers to make the change so that they can deliver a high-quality product.

The Daily standup, product backlog, sprint demo, and retrospective are the things that drive each feedback loop. First of all, in the daily standup, that meeting is for an update on the project. Based on what the scrum master sees, they present feedback to the team. The developers then, must make a change. Also, the scrum master must remove any obstacles that they hear about in the meetings so that the project can run smoothly.

In the product backlog, the product owner sits with the developers so they can develop feedback loops. The backlog is an everchanging list that is always added to have a wide variety of ideas. If the product owner does not sit with the team, then this could stop any additions to the back log and the developers may not be creating off the top user stories.

The sprint demo creates the demo for the stakeholders to vision the product. In a demo, if the stakeholders are asking the same questions, this means that the feedback loop is not working well. To fix this a “heard it did it board” could be the solution. This board will help the team see what problem need to be solved and once they are done, they are put into the did it section so that they know thing are being met at the end of demo. This will also help prioritize task to implement the most important task.

Lastly, in the retrospective is a way to get feedback. The project manager is there to make sure that people are talking and exchanging ideas. Open ended questions are a good way to start getting people to talk. This will help keep the product adapting and changing. Making sure that all four areas are talking will make sure you are getting effective feedback. Lastly, off that feedback, this will help get the team through any obstacles and devlop a high level product.

Works cited

Rose, Doug. “Listening to Feedback.” Lynda.com - from LinkedIn, 29 Sept. 2015, www.lynda.com/Business-Skills-tutorials/Listening-feedback/175075/438005-4.html.