---
# System prepended metadata

title: Implementing user feedback

---

# Implementing user feedback

## Attendees

* Katharina
* Georgia
* Daniel
* Saima
* Thomas S
* Chris

### Summary of user feedback (overview)
* Results mixed by topics, and some especially important information highlighted
* Prototype will need updating or a note explaining it will look different each time if the link updates automatically 
### Prior experiences

"Example from features.md" https://github.com/fjAutisticaCitizenScience/AutisticaCitizenScience/blob/documentation/project-management/platform-requirements/features.md
- Building a healthy community
    #### Definition
    ```
    Ensuring that those who wish to contribute or engage with the project understands how to do so.
    ```
    #### Management
    
    | Project Management Issues |
    |---------|
    | #128 - Update timelines for agile workflow process |
    | #129 - Get comfortable with GitHub |
    | #159 - Explain the Project Management Board Swim lanes columns |
    | #246 - I need to add a GitHUb tutorial on this repo |
    | #255 - Glossary of Technical terms |
    

    
    | Design Issues |
    |---------|
    | #176 - Document the process of how we will get feedback from the community |
    | #179 - Clarify how people can give feedback on the sprint demo video|
 
    
    | Coding Issues |
    |---------|
    | - |


    #### Supportive community discussion
    | Source  | Speaker | Statement |
    |---------| ------- | --------- |
    | Document A | A | I would like this so that |
    | Document A | B | I would like this so that |
    | Document B | C | I would like this so that |

    #### Prioritisation History
    | Priority (H/M/L)  | Date of prioritisation | Reasoning |
    |---------| ------- | --------- |
    | L | 17/07/2020 | Development efforts are focussed at the moment on core feature. This is not a core feature |

#### (Positive, negative, problems to avoid, best practices)
* have individual ideas as an issue each, link issue to the document
* labelled, get added to project board
* **vague** issues --> acceptance criteria (added in backlog refinement sessions)
* priority setting by labelling issues
* priorities set in discussion with kirstie and georgia
* milestones
* not just creating new issues, talking through issues that already were defined 
* working with labels
* controversy about features
* prioritisation
* issues need to be concrete and actionable (but also keep a record of controversy)

### Ideas
* **prioritise** issues for development
* similar process like with focus groups: going through document, taking concrete suggestions from there, creating issues, sprint planning meeting
* adding new community input to existing issues
* new column in project management board for user feedback 
* including the key in issues
* 2 audiences of items that can be actioned by a certain audience: delivery and research
* single source of truth (project board)
* capture, curate, actionable
* mind mapping tool

### Next steps
* 1. Mindmap with user feedback (Katharina [+Kirstie, Georgia, Daniel?])
* 2. Consolidate mindmap with existing issues/work on GitHub (Thomas, Daniel)
* 3. Create issues for product backlog (Thomas, Daniel?)
