Project Failure Analysis Patterns (Part 1)
Recall from my motivation for this pattern series the analogy between the following entities:
-
Computer Application/Process - Team
-
Thread of activity - Team member
-
Operating system - Company organization and management
-
Computer system - Company organization and management plus teams
-
User process dump - Team state snapshot
-
Kernel memory dump - Organization state snapshot
-
Complete memory dump - Organization state plus teams internal state snapshot
-
Exception - Fault, mistake
-
Crash or hang - Failure
The first pattern is called Multiple Faults and it is a direct mapping from application crash analysis Multiple Exceptions pattern. The running instance of a computer application (process) can experience multiple exceptions from different execution threads before it hangs or crashes. The latter causes the process to disappear from external observers watching Task Manager. The same can be true for any functional team. Multiple faults from different team members can happen and if a team fails we shouldn’t attribute the overall failure to just one member’s fault that is on a surface but look for other possible mistakes too.
- Dmitry Vostokov @ ManagementBits.com -
AnnouncementsComing Soon:
Debugging Notebook: Essential Concepts, WinDbg Commands and Tools
Crash Dump Analysis for System Administrators and Support Engineers
New Magazines:
Debugged! MZ/PE: MagaZine for/from Practicing Engineers
New Books:
Memory Dump Analysis Anthology, Volume 3
First Fault Software Problem Solving: A Guide for Engineers, Managers and Users
x64 Windows Debugging: Practical Foundations
Also available:
Windows Debugging: Practical Foundations
DLL List Landscape: The Art from Computer Memory Space
Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov
WinDbg: A Reference Poster and Learning Cards
Memory Dump Analysis Anthology, Volume 2
Memory Dump Analysis Anthology, Volume 1
New Children's Book:
