Professional Documents
Culture Documents
11 Laws of IT Physics'
11 Laws of IT Physics'
com
11 ‘Laws of IT Physics’
● Date: November 21st, 2008
● Author: Michael Krigsman
● Category: Project Management
● Tags: Project, Information Technology, Planning, Strategy, Management, Michael Krigsman
●
During testimony before Congress, Norm V. Brown presented what he calls “Laws of IT
Physics.” These “Laws” highlight hidden pitfalls the hurt many projects and help explain why
some projects succeed while others fail.
—————————————————————————————————————
This is a guest post from Michael Krigsman of TechRepublic’s sister site ZDNet. You can follow
Michael on his ZDNet blog IT Project Failures, or subscribe to the RSS feed.
Given high rates of failed IT projects, it’s helpful to examine first principles that underlie
successful technology deployments. Even though devils live in the details, understanding basic
dynamics behind successful project setup, execution, and management is important.
During testimony before Congress, in a hearing titled “The Dismal State of Federal Information
Technology Planning,” Norm V. Brown, Executive Director of the Center for Program
Transformation, an IT failures think tank, presented what he calls “Laws of IT PhysicsTM.”
These “Laws” highlight hidden pitfalls the hurt many projects, and help explain why some
projects succeed while others fail. They recognize that successful IT project delivery is primarily
about managing people, process, and deliverables. Yes, technology is important, but the people
side comes first. Here’s the list, with slight editing:
This is the silent killer! Lewis Cardin, senior project portfolio management analyst at Forrester
Research, calls this “first number syndrome,” where senior management becomes tied to initial
estimates and refuses to accept change.
It’s completely unreasonable not to expect that lengthy projects will evolve over time. Change
isn’t necessarily bad; for example, business needs may evolve and force a corresponding project
adaptation. Balancing shifting priorities through scope changes is the difficult part of this
equation.
According to Wikipedia, in general relativity an event horizon is a boundary inside which events
cannot affect an outside observer. Combine a complex technical environment with byzantine
project scheduling and workflow, and meltdown becomes likely. Simplify wherever and
whenever possible.
6. You can’t manage what you can’t see. Track Project Status and Progress
against small, testable, incremental product deliverables and use quantitative
project parameters, such as Earned Value, to make projects visible and
manageable.
7. Not controlling the right things assures failure. Use well established best
Yes, testing matters a lot. Just ask retailer J.Crew, which lost the ability to ship product to
customers after deploying a new web site and content management system without sufficient
testing.
Testing isn’t rocket science, but it must be performed in a disciplined and consistent manner.
Every major IT project consists of a partnership I call the Devil’s Triangle: customer, technology
provider, and system integrator working together to achieve a common goal. These groups have
interlocking and sometimes conflicting agendas, which makes management a balancing act of
priorities.
Most consulting companies are honest folks doing the right thing for their customers. Still, you
need to protect yourself from bad apples by carefully controlling contracts, incentives, and
penalties.
Although these 11 laws are oriented toward government projects, the lessons are equally
applicable to projects in the private sector. The list is worthy of your thoughtful consideration.
Trackbacks
The URI to TrackBack this entry is: http://blogs.techrepublic.com.com/tech-manager/wp-
trackback.php?p=640
No trackbacks yet.
● My Updates
● My Contacts
●
Popular on CBS sites: MLB | Spore | iPhone 3G | Paris Hilton | Antivirus Software | GPS |
Recipes | Shwayze | NFL
© 2008 CBS Interactive Inc. All rights reserved. | Privacy Policy | Terms of Use