Gerardo Ortega

7%
Flag icon
A proper postmortem should always contain an explanation of what was learned and what is going to change as a result of the learning experience. Then, make sure that the postmortem is readily accessible and that the team really follows through on the proposed changes. Properly documenting failures also makes it easier for other people (present and future) to know what happened and avoid repeating history.
Software Engineering at Google: Lessons Learned from Programming Over Time
Rate this book
Clear rating
Open Preview