Software projects are notorious for being late, over budget, and delivered with poor reliability. In the past this has often been due to ambitious attempts to take on the construction of large amounts of functionality within very aggressive market deadlines. Increasingly, one solution involves partitioning large release projects into smaller subsystems, each developed by separate smaller teams. Then the subsystems are integrated and validated to provide the final product release.
Article
          Case Study: Using Metrics to Ensure High Reliability of Software Releases
By Jim Greene
  Posted July 1, 2001 | Technology | Cutter Benchmark Review 
    
        Don’t have a login?
    
    
      Make one! It’s free and gives you access to all Cutter research.
    
    
    
    
  

