GeekArticles 
Testing Change Management
Testing Change ManagementSoftware Testing Turnovers
As companies grow and become more sophisticated they recognize the need for analysts, both business and QA, to support their Information System functions. Often the practice of software turnover to the QA team is a matter of informal notification. This notification at best includes a module list, functional changes, and a deadline for moving the changes into production. This arrangement for turnover naturally developed because all organizations start with an IS department that has a minimal development staff. It should be the role of a proactive testing department to increase its own involvement in the development process define its participation in the life cycle process, and to manage this change.
Sponsored Links
Read Next: Project Planning Process-Part I
Related Topics
Subscribe via RSS
Change Management
- Change Management Best Practices
- Change Management
- Managing and Controlling Workspaces
- Streamlined Change Request Management
- Software Testing Turnovers
- Project Planning Process-Part I
- Project Planning Process-Part II
- The Four Quadrants of Techno-Management
- Sarbanes-Oxley and the Need to Audit Your IT Processes
- QUALITY ASSURANCE: The Customer’s Advocate in Product Companies
Sponsored Links
About |
Privacy Policy |
Submit Resource |
Submit Article |
Contact |
Site Map
Copyright © 2009 GeekArticles.com. All Rights Reserved.
