New Board type to be used in retrospectives
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
This is a request for a new board (type). One that can be used during retrospectives.
Describe the solution you'd like
- At the beginning of a retrospective the board shows some empty columns.
- The columns represent a subject to be discussed/reviewed. Like, 'What did you like', 'What didn't you like' and 'Try next', etc
- The columns are created by someone, or can be selected from a default set
- Participants can add cards to the respective columns.
- My cards are visible, while cards added by others (in the same session) are not visible yet.
- After some countdown time, all cards are shown
- While reviewing/discussing the topics on the cards - similar cards can be merged into one card
Next:
- Topics can be voted for, with a thumbs up
- After voting 'someone' can order the cards. The cards with the highest votes are stored at the top.
Next:
Add a new column (when it is not available), for example called 'Action':
- Move the highest scored cards from the other columns to the Action column
- Allow for additional text to be added to the Actions card.
People now know what to do. Quick and easy :)
The cards in one column should have the same background color. Green, Purple, Orange, for example.
Many more things can be envisioned. But with the above functionality to start with, it would be nice board already.
Describe alternatives you've considered
easy retro
Additional context
See previous item, for examples.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing board implementation and scoping which retrospective behaviors belong in an initial release; define acceptance criteria for columns, private cards, reveal timing, merging, voting, ordering, and action cards before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100