COURSE 5125 | 2-DAY SESSION
Managing Software Development with Metrics

---

Metrics provide key information needed to make decisions critical to project success. You cannot build quality software or improve your software process without metrics.

How to:

• Increase insight and reduce risks by using metrics throughout the life cycle
  
• Provide visibility into the‘real’ status of the project
  
• Measure and track progress, productivity, and quality goals
  
• Take timely corrective action due to early detection of potential problems
  
• Develop software that is less‘complex’, and therefore easier to test and maintain
  
• Track and manage fault reporting and removal
  
• Increase the quality of testing by finding areas of the program that have not been tested
  
• Increase understanding of your software development process
  
• Get started - gain a powerful core set of metrics
  
• Integrate metrics into the development process
  

Bonus: When you attend: In class, you'll receive and use copies of Waltzing With the Bears, Managing risk in Software Projects, by DeMarco and Lister, and Managing Software Development with Metrics by Al Sorkowitz.

20 Immediate Benefits of Participating in this Workshop:

1. Learn“best practices" metrics for each phase of the life cycle.
   
2. Set -up and analyze these metrics.
   
3. Track progress as well as changes in the Requirements Phase.
   
4. Produce better requirements by learning criteria for good requirements.
   
5. Improve testing by learning to differentiate between testable and non-testable requirements.
   
6. Track progress and stability in the Design Phase.
   
7. Save costs by reducing the complexity in the Design Phase.
   
8. Track progress in the Unit and Integration Test Phase.
   
9. Reduce testing costs by quickly identifying paths for testing.
   
10. Increase the quality of testing by finding areas of a program that have not been tested.
    
11. Modularize programs to reduce complexity.
    
12. Calculate a programs complexity.
    
13. Improve project management by tracking progress in unit, integration and system testing.
    
14. Understand the cost of inadequate software testing .
    
15. Provide insight into the quality of the software.
    
16. Evaluate the developer’s ability to fix known bugs.
    
17. Track the developer’s ability to maintain planned staffing levels.
    
18. Track changes in utilization of scarce computer resources.
    
19. Track rework activities.
    
20. Reduce risk by tracking changes in program size.t