【正文】
9。CyberQ Consulting 14. Insufficient tracking of software progress against estimates 15. Configuration management inconsistently implemented on current projects 16. Inadequate procedure to control changes to requirements allocated to software subsequent to requirements review 169。CyberQ Consulting 17. Lack of effective configurations management on all deliverables (eg. Requirements, documentation, code and test cases) 18. Lack of anizationwide coordination of process activities 19. Users, systems, software, and test do not have effective collaboration in defining system capabilities 169。CyberQ Consulting 20. Process metrics are not uniformly defined, collected, and analysed 21. Senior management’s review of project progress on process and quality is informal or nonexistent 22. Review of subcontractor schedule and quality goals restricted to prime’s milestone reviews 169。CyberQ Consulting 23. Ineffective risk management process in place 24. Ineffective use of metrics from anizational process database 25. Detected errors not traced to their root cause