|
|
|
Better Software Conference & EXPO 2006 Concurrent Sessions
Go To: Agile Development | Managing Projects and Teams | Measurement | Outsourcing | Plan-Driven Development |
Process Improvement | Quality Assurance | Security | Special Topics | System Requirements | Testing
View by Date
| Quality Assurance | | | Wednesday, June 28, 2006 11:30 AM |
Unintended Consequences of a Capability Maturity Mismatch�Evidence from a Quality Audit
Michael Harris, David Consulting Group
In this presentation Michael Harris describes the findings of a quality assurance audit (PPQA) of the offshore outsourcing arm of a major U.S. software development company in late 2005. As the executive in charge of much of the development and as a member of the PPQA audit team, the Michael has a singular perspective on the expectations and the reality of the project. This presentation explores one particular aspect of the audit findings�the manifestations of the different CMMI� maturity levels of the onshore and offshore organizations. Take away suggestions for taking advantage of this mismatch situation instead of suffering from it.
� Review a quality assurance audit (PPQA)
� Explore the different CMMI� maturity levels of onshore and offshore organizations
� Take advantage of mismatched outsourcing situations |
| | | Wednesday, June 28, 2006 1:45 PM |
When the Customer Does Not Know Best
John Scarborough, Aztec Software Inc
Failure to really understand business requirements, technical specifications, and schedule dependencies has embarrassed more than a few test teams. Before you assign the first test engineer to a project, sit down face-to-face with the customer and keep asking questions until you fully understand the scope of the system or application under test, how they will use it, and what success looks like through their eyes. A full needs analysis is the best preparation for designing a test strategy that will deliver exactly the data your customer needs to decide when they can ship or go live with their software. John Scarborough explores the critical areas of inquiry for conducting a needs analysis, using examples from projects he has worked on over the last five years. Learn to exercise deliberate, critical thinking while following a proven, systematic approach for conducting analyses.
� A systematic approach to performing a needs analysis from a testing perspective
• Templates and tips for conducting needs analysis interviews
• Documentation to support a needs analysis |
| | | Wednesday, June 28, 2006 3:00 PM |
Essential Software Quality Planning
Tony Raymond, New Harbor Technical Management
An old�yet still true�saying is �You can�t test quality into a software product.� By planning for the quality expected in your software, your team and management will focus on the big picture�integrating development methods, the test processes, and the customer and product requirements within the framework of a quality assurance perspective. Starting with the key element of quality planning and its benefits, Tony Raymond explains how to derive quality objectives from requirements using a �just enough� balanced approach. He introduces methods to confirm that the development lifecycle processes are consistent with quality objectives and discusses the relationship of the quality plan to the test plan. Take back examples of quality planning and test planning templates to use in your next project.
� How to define �just enough� quality objectives
• Validate development process objectives, methods, controls, tools, and standards
• Tie together the development lifecycle, test process, and requirements |
| |
|
|
