Dear Bob ...
I like the idea of doing postmortems, which you discussed in a recent Keep the Joint Running. Learning from mistakes or even just from events and observations can't be a bad thing. I have a few questions for you about them, if you don't mind.
[ Also on InfoWorld: "The best way to conduct an IT postmortem" | Get sage advice on IT careers and management from Bob Lewis in InfoWorld's Advice Line newsletter. ]
- Not Quite Dead
Dear NQD ...
I don't mind a bit. Here are your questions, with my answers following.
1. Who should be involved in doing a postmortem?
It should be the project manager, core and extended team, business sponsor, and possibly other major stakeholders if they had significant involvement.
2. What is the appropriate level of resources to spend on doing a postmortem?
Same answer as above; the meeting should last no more than an hour. The PM should be the one to document the results.
3. On what kinds of projects/efforts should postmortems be done? Failures only? Successful projects (postvivum?), killed projects?
All, at least until success is so routine that the organization has reached the point of diminishing returns.
4. To whom should the results be communicated?
It depends on how the company has organized its PMs. If there's a formal PMO, communicate the results to it. It should have a well-established mechanism for updating the company's PMs on new lessons learned and modifications to company standard practice.
Or someone in the company is almost certainly an informal focal point of project management practices (the CIO, head of app dev, and head of organizational development are possibilities). Whoever that is should maintain a distribution list consisting of everyone who has ever managed a formal project in the company. The documentation should then be sent to that list.
If neither of these is the case, the PM should send the results to everyone he/she thinks might be interested -- there's almost certainly an informal network of PM-like employees who know who each other are and help each other out.
This whitepaper explains the terminology and concepts behind Data Replication technologies and establishes some sizing rules through worked examples. Learn the new paradigm in disaster tolerance—protect data anywhere.
Download now »
Server virtualization is a popular option for dealing with mounting datacenter costs. Another equally promising approach is the use of an Application Delivery Controller. Citrix NetScaler provides a low-cost way for organizations to reduce their server count and accrue cost savings from a reduction in space, cooling, power and personnel.
Download now »
The emergence of WLANs has created a new breed of security threats to enterprise networks.
Included in HP ProCurve WLAN solutions is security technology that alleviates threats from WLANs through:
* Monitoring wireless activity inside and out of the enterprise
* Classifying WLAN transmissions into harmful and harmless
* Preventing transmissions that pose a security threat to the enterprise network
* Locating participating devices for physical remediation
Effectively address data protection challenges, implementing solutions that help store and protect business–critical data while cutting costs and improving efficiency and reliability.
Download now »
Sign up to receive InfoWorld Resource Alerts
305 Recommendations
