To determine whether you do have a system problem, you need to perform three tests. These tests will show if delays and cost overruns are arising for one or two reasons. The first could be because the components of the product don’t interface with each other as a system. This is analogous to putting together a child’s bike. If the parts in the box don’t fit, then you won’t have something that looks like a bike. The second could be due to incomplete requirements that went into building the components, which would result in a system not functioning as expected. In the bike example, even if the parts do fit, the bike may not work as intended. For instance, the bike doesn’t stop properly because the brakes don’t have proper contact with the wheels.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|How To Recognize You Have A Systems Problem.pdf||application/pdf||80.34 KB||English||DOWNLOAD!|