Management Bits and Tips

There is something similar, at least metaphorically, between computer system crashes and hangs and software project failures. Software projects deliver software that crashes and these software failures via negative feedback loop either slow projects down or simply lead to their abandonment. The structure of a software development team resembles that of a running application (called a process) with team members acting in parallel (threads) and the structure of operating system with multiple running processes competing for resources resembles a software company struggling to stay alive. When projects fail there is something left as artifacts available for study and the same is true for crashed processes or operating systems leaving crash memory dumps behind for postmortem analysis.  

In some future posts I’m going to map Crash Dump Analysis patterns to Project Failure Analysis patterns and see what comes out of this attempt.

- Dmitry Vostokov @ ManagementBits.com -

Announcements

Coming 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:

Baby Turing

This entry was posted on Tuesday, December 18th, 2007 at 5:20 pm and is filed under Project Failure Analysis Patterns. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.