All About Agile | Agile Development Made Easy!
Feedback mechanisms
I'd like to hear details about how you get feedback from users and other stakeholders.
Tags: feedback
Views: 0
Replies to This Discussion
-
Permalink Reply by Kelly Waters on -
Hi Shawna. Scrum has some feedback mechanisms built in. Before I detail, did you have any particular types of feedback or stakeholders in mind?
Kelly.
-
Permalink Reply by Shawna on -
We do sprint reviews (which currently don't give us a lot of feedback) and retrospectives.
We use Jira with Greenhopper, so our internal users (and currently one external user) have access to communication through the ticketing system, and can be prompted that way. We have also occasionally used a forum to have discussions among our external users. Obviously, we reach out to users on the phone or via email on occasion as well, but we need to take things to the next level.
I am especially interested in hearing about specific interactions with internal and external users within a single sprint (to start with) regarding the stories in the sprint, and how the team made it a habit.
-
Permalink Reply by Kelly Waters on
-
For face-to-face feedback from internal users, we generally find our stakeholders and internal users hang around after the daily stand-up and talk about individual user stories being developed directly with the developers. This is obviously a good informal mechanism and provides direct feedback little but often, which personally I think is good so the team can make small adjustments as they go rather than hear big surprises at the end of the sprint or even later in the project. I wonder if you could potentially make the sprint review more interactive, as a way of getting feedback between sprints as well. If you have daily builds or a continuous integration environment, the product should always be available for review and maybe it's a case of explicitly inviting feedback on a regular basis to ensure that you never go too long without the chance to adjust what you're doing. Obviously this might also be practical for external users if they can't hang around after the stand-up, so long as they can access your development/QA or preferably your UAT environment.
Kelly.
-
Permalink Reply by Kevin Johnston on -
the primary method I feel is by being as transparent about what is being done as possible...daily stand ups, demos to anyone and everyone that has a stake in the system, provide access to DONE software by pushing the software to demo machines as often as possible.
© 2012 Created by Kelly Waters.
