Skip to main content
The Workplace

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.

8
  • 17
    Seems like this question is a much better fit for softwareengineering.stackexchange.com . If you want to generalize into how teams of all types learn from mistakes, OK, fine, but the question seems scoped quite specifically to issues of software development.
    – CynicallyNaive
    Commented Sep 10, 2020 at 23:59
  • 12
    I don't think you understand agile at all - the retrospective meeting at the end of each sprint is intended exactly for this sort of analysis and reflection, with the end result being concrete suggestions for improvement that you integrate into the next sprint. At the end of that sprint, you use its retro to evaluate whether what you did had the desired outcome, and incorporate that feedback into the next sprint - rinse repeat. Agile is not about defining universal processes that work for every company, it is about being quick to react and willing to adapt as relevant for your company.
    – Ian Kemp
    Commented Sep 11, 2020 at 12:11
  • 1
    Don't you think that comes down to two separate, largely unanswerable Questions? How do big development teams (anything)? How does anyone learn from mistakes?
    – Robbie Goodwin
    Commented Sep 11, 2020 at 21:56
  • 1
    I just want to comment that it's far better to learn from other companies mistakes rather than your own. Meaning that, following established best practices is far better than forging your own path and coming to the same conclusions. Not really an answer, but a focus on preventative analysis is likely to be received better than a post-analysis, where people are fearful of the blame game.
    – Gregory Currie
    Commented Sep 12, 2020 at 8:02
  • 1
    @IanKemp In my experience retrospectives generally only identify problems which occured in the last sprint or two (which is important don't get me wrong) but often miss longer term trending problems, which is what I think OP is trying to ask about. E.g., I watched a talk recently where, after writing and fixing millions of lines of code, they discovered the way they were using if statements was causing 90% of their bugs. I think OP wants to learn ways of discovering those kind of bug root causes.
    – DarcyThomas
    Commented Sep 13, 2020 at 1:23