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 |
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.
1
vote
Is it a good idea to show a 'story points by developer' graph at retrospectives?
Statement #1: Story points is not a measure of individual contributor productivity.
Statement #2: Story points are a relative effort & complexity measuring tool.
Now some people infer from the above s …
1
vote
As a Scrum Master, how to speak to a developer about his delays?
You'll get a lot of 'ideal' Scrum Master behavior which if not favor at least do not harm engineers; but they do harm you as a leader / scrum master in the organization.
Some might tell you not to app …