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 | |
Results tagged with retrospective
Search options not deleted
user 8639
Retrospective is a meeting held by a project team at the end of a project iteration of its inspect-and-adapt or continuous improvement process. Use `sprint-retrospective` instead for Scrum-specific retrospectives. Do NOT use this tag for questions about postmortems; use the `postmortem` tag instead.
4
votes
How to capture and document sprint retrospective results
team, we try to group them into 3 main groups:
What went well (Keep doing)
What went poorly (Stop doing)
Ways to improve (Try doing)
I then collect these 3 "piles" of input and use them to craft a retrospective …
- 41