Project Failure Analysis Patterns (Part 2)

What is an equivalent to computer memory in organizations and teams? It is the collection of various artifacts including project documentation, source code, financial documents, etc. What is a computer memory corruption? It is a deviation from expected memory contents that may or may not lead to a crash or a hang but the chances of that are increasing over time. Metaphorically we can consider deviations from requirements or expected documentation content to be some sort of a corruption that might slowly lead to a project failure over time. Surely “project memory” or “organization memory” is dynamic or heap-like in nature as documents are added to a pile or removed from it. Therefore we have just established the mapping between Dynamic Memory Corruption pattern from crash dump analysis domain to Project Artifact Corruption pattern. 

- Dmitry Vostokov @ ManagementBits.com -

One Response to “Project Failure Analysis Patterns (Part 2)”

  1. Dmitry Vostokov Says:

    Incremental and iterative processes coupled with appropriate tools mitigate risks of artifact corruption if documentation is updated with each project iteration

Leave a Reply