Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
6
votes
How can we improve the feedback loop when releases require significant compliance work?
You can get continuous feedback from an internal testing team. You could even propose to your customer to review select interim releases and provide feedback. … Each Sprint will consist of an entire internal cycle; coding, testing the release document, testing the new features, and feedback. …
0
votes
Best practices for collating and analysing client feedback from multiple departments
I would suggest creating various categories that the reporter fills in, so that you can sort and group them and hopefully get the similar ones together.
A few dropdowns may suffice - here are some sug …
1
vote
How to collect stakeholder feedback on prioritizing features?
One way would be to set up a quick survey - there are sites that let you do this for next to nothing.
Rank each feature between 1 (must have) to 5 (hardly necessary).
Or else "Yes, Maybe and No"
…