Implementing Feedback in Agile development [closed]

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

This question does not appear to be about programming within the scope defined in the help center.

Closed 4 years ago.

Improve this question

I just need to know about planning product development in a particular scenario.

Suppose, If I planned my sprint and executed it and then I submitted the product url for feedback and received the response from my product owner. In that case, in which sprint(Current sprint or next sprint) should I Implement the feedback responses. What is a normal procedure for this in agile development.

Can some one clarify. Thanks.

Answer 1

When you say you "executed" the sprint, this means that you completed the code for the feature(s) you committed to and that the feature(s) passed the acceptance tests your Product Owner helped write. Absent passing these tests, the feature isn't done--at least not according to Scrum (which I presume you are using if you mention a sprint and Product Owner).

If a feature doesn't pass, it isn't done. If it passes, then it is. Now at the demo at the end of the sprint, maybe other stakeholders feel the feature should do something else in addition or whatever. In that case, the new feature is added to the Product Backlog as a user story and sized and prioritized like any other.

What you describe might occur during a sprint where you just show the Product Owner something to satisfy his or her curiosity, but the only feedback that matters is passing acceptance tests that indicate the feature is production-ready.