You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 2I'm not sure that "push back from the PM" is the most useful framing. The entire team, as a whole, should want to improve their process—that's what the retrospective is for—and all of the issues you've identified are great things to consider as part of that discussion, but I think it's most useful to think of it as "how can the team help ensure that the estimates provided by sprint goals are more useful in the future?" rather than a PM pushing back on the team for not accomplishing tasks.Zach Lipton– Zach Lipton2019-09-21 00:20:27 +00:00Commented Sep 21, 2019 at 0:20
- 1I think you get to the heart of the problem. The PM has to bring this up its vital to understand why the project is late, but the #1 reason is going to be 'estimates were wrong' for whatever reason. (and #1 reason for that would be PM didnt like high estimates!)Ewan– Ewan2019-09-21 08:50:53 +00:00Commented Sep 21, 2019 at 8:50
- To me, this is clearly the best answer so far. +1angryITguy– angryITguy2019-09-23 06:32:13 +00:00Commented Sep 23, 2019 at 6:32
- How about we refer to 'pushback' (which implies a potentially antagonistic approach) as "questions" which seems more neutral and effective to me?Michael Durrant– Michael Durrant2019-09-23 11:05:03 +00:00Commented Sep 23, 2019 at 11:05
- 1@MichaelDurrant et al. Fair enough - I've modified the wording of the first paragraph.Robbie Dee– Robbie Dee2019-09-23 11:50:52 +00:00Commented Sep 23, 2019 at 11:50
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you