1
March 4, 2009 10:03 AM
Posted by: Jaideep Khanduja
business requirements, change management, Code library, Code repository, development plan, implementation plan, organizational goals, product development, project close-out, project documentation, project management, project methodologies, Project Plan, project standards, Quality Goals, requirements analysis, Risk Management, Risk Plan, software development, software development methodologies, software development standards, Software Project, software quality, Software Repository, software testing, SQA, SQC, test case, test case repository, Test Plan, test standards, time to test, top management requirements
10 top “Do this if you want blunders!” in Software Development and Software Testing
Posted by: Jaideep Khanduja
business requirements, change management, Code library, Code repository, development plan, implementation plan, organizational goals, product development, project close-out, project documentation, project management, project methodologies, Project Plan, project standards, Quality Goals, requirements analysis, Risk Management, Risk Plan, software development, software development methodologies, software development standards, Software Project, software quality, Software Repository, software testing, SQA, SQC, test case, test case repository, Test Plan, test standards, time to test, top management requirements1. Quality Goals are meant only for Quality Department: No department other than quality (project management, product development, documentation, general management etc.) has to read, understand and learn about the quality goals of the organization. It is only the responsibility of...
0 Comments
RSS Feed
Email a friend
