|
|
Baby Steps-Testing Therapy for Developers Learn from a "developer-in-recovery" the strategies for overcoming testing phobia and testing animosity among developers. Now a "convert" to disciplined, quality-oriented software development, Susan Joslyn provides you with approaches that are helpful in educating developers, most of whom actually want to make a better contribution to quality practices. The testers who must beg, cajole, and trick their developers into using them will benefit greatly from attending this session.
|
Susan Joslyn, SJ+ Systems Associates, Inc
|
|
|
Critical Skills and Effective Attitudes for Testers What distinguishes good testers? Some characteristics explained in this presentation:
- the right attitudes
- the appropriate skills
- continuous skills growth
|
Rex Black, Rex Black Consulting Services, Inc.
|
|
|
The Role of Information in Risk-Based Testing With risk-based testing, you identify risks and then run tests to gather more information about them. Formal risk analysis is often necessary for identifying and assessing risks with new domains or technologies. A common problem, however, is how to assess risks when you have little information. Learn how to use testing to identify risks, reach team agreement on risk magnitude, and identify actions which allow these risks to be understood and mitigated.
|
Bret Pettichord, Satsfice
|
|
|
Collaboration Between Development and Testing Personnel is a Key to Success Applications are often designed and developed with little regard for testing. Functional and Load/Configuration testing needs to be a collaborative effort between the development and testing groups for a project to be most successful. Everyone needs to "own" some of the testing responsibility. Learn how to accomplish an ongoing collaboration between application architects, designers, developers, and QA/testing personnel to identify and resolve problems (defects) in an efficient and timely manner.
|
Tom Igielski, Upstream Solutions, Inc
|
|
|
Organization: The Forgotten Dimension Explore the software project manager's actual, perceived, and desired position in an organization. Learn how the differences in these three views-coupled with the understanding of roles, responsibility, authority, and accountability-may be more important to a manager's success than the method used to manage the project. Discover techniques that leverage "difficult" organizational structures and cultures to enable the free flow of information that is critical to process improvement and project performance.
|
Mark Servello, Change Bridge, Inc.
|
