Timeline for How do big development teams learn from their mistakes?
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2020 at 6:00 | history | tweeted | twitter.com/StackWorkplace/status/1305748200691765248 | ||
| Sep 14, 2020 at 7:33 | comment | added | Jim | @DarcyThomas: You are correct! | |
| Sep 14, 2020 at 7:32 | comment | added | Jim | @IanKemp: I thought so but I was under the impression that the retro is more about highlighting collaboration/communication issues not about technical problems | |
| Sep 13, 2020 at 1:23 | comment | added | DarcyThomas |
@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.
|
|
| Sep 12, 2020 at 8:02 | comment | added | Gregory Currie | 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. | |
| Sep 12, 2020 at 6:44 | comment | added | fraxinus | Wrong assumption? Because they don't. | |
| Sep 11, 2020 at 21:56 | comment | added | Robbie Goodwin | 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? | |
| Sep 11, 2020 at 17:59 | answer | added | user48276 | timeline score: 0 | |
| Sep 11, 2020 at 14:29 | answer | added | bethlakshmi | timeline score: 1 | |
| Sep 11, 2020 at 12:11 | comment | added | Ian Kemp | 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. | |
| S Sep 11, 2020 at 6:26 | history | suggested | sixtyfootersdude | CC BY-SA 4.0 |
Fix line breaks
|
| Sep 10, 2020 at 23:59 | comment | added | CynicallyNaive | 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. | |
| Sep 10, 2020 at 20:29 | review | Suggested edits | |||
| S Sep 11, 2020 at 6:26 | |||||
| Sep 10, 2020 at 17:10 | answer | added | Old_Lamplighter | timeline score: 2 | |
| Sep 10, 2020 at 16:26 | answer | added | Peteris | timeline score: 2 | |
| Sep 10, 2020 at 15:45 | history | became hot network question | |||
| Sep 10, 2020 at 15:38 | answer | added | mxyzplk | timeline score: 39 | |
| Sep 10, 2020 at 11:10 | answer | added | user | timeline score: 103 | |
| Sep 10, 2020 at 9:59 | answer | added | Robin Bennett | timeline score: 4 | |
| Sep 10, 2020 at 9:11 | review | Close votes | |||
| Sep 16, 2020 at 3:02 | |||||
| Sep 10, 2020 at 8:36 | answer | added | Kilisi♦ | timeline score: 2 | |
| Sep 10, 2020 at 7:58 | answer | added | berry120 | timeline score: 8 | |
| Sep 10, 2020 at 7:44 | history | asked | Jim | CC BY-SA 4.0 |