Project Management

Studies have shown that over fifty percent of software defects are attributed to poorly defined requirements. From a process improvement perspective, it is imperative that project managers establish a more effective and efficient way of defining and tracking business requirements. Jeff Tatelman describes a "how to" approach for developing a practical automated regression testing process using a traceability matrix and business event scenarios. Learn how requirements-based testing-coupled with a data-driven approach to test automation-can solve problems that plague most software development projects.

Topics covered in this presentation include: Why and when to trim the test suite; How to select tests to run with
Coverage Analysis System (CAS) tools; Testing Code Changes before push; How we create CAS databases; and When CAS methods are not useful.

How do the things you hear at a conference relate to the choices you make on the job? If you really want to help improve how your projects work, don't be a passive transceiver of "best practices." Instead, be an active thinker who understands why methods work and when to apply them. James Bach illustrates how some often-recommended practices aren't necessarily helpful unless you use your skill and judgment to adapt them to your particular situation.

Are you looking for a way to effectively set the expectations of senior management? The Functional Readiness Matrix (FRM) is a decision-making tool that offers a simple way to represent test progress based on the functional areas or features of an application. By enabling the test team to track actual test progress against the implementation goals established early on, the FRM allows for the presentation of valid test metrics to management in a way they can understand.