Skip to main content

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.

6
  • extended sprint retrospective is in order I was under the impression that these retrospectives are meant to deal solely with communication and collaboration issues
    – Jim
    Commented Sep 10, 2020 at 8:01
  • you're looking to have a post-mortem is that a standard methodology I can read about?
    – Jim
    Commented Sep 10, 2020 at 8:01
  • 1
    @Jim Typically a retrospective would do just that, but if ways of working and communication could be the root cause of those technical issues, then it could still be appropriate (these things aren't set in stone.) They're both standard terminology, and often used interchangeably - personally I tend to think of a retrospective more as a regular occurrence, and a post-mortem as more of a one-off around a bunch of issues, but YMMV when searching around.
    – berry120
    Commented Sep 10, 2020 at 8:05
  • @jim, you could try the 5-why's (en.wikipedia.org/wiki/Five_whys) to get the root cause of the problem. Commented Sep 10, 2020 at 9:00
  • @RobinBennett: Interesting! How would that be applied as a "formal" process?
    – Jim
    Commented Sep 10, 2020 at 9:20