|
|
|
|
|
|
|
| |
|
|
| |
| |
Jeff Payne, Coveros, Inc.
Many organizations refer to their test teams and testers as QA departments and QA engineers. However, because errant systems can damage—even destroy—products and businesses, software quality must be the responsibility of the entire development team and every stakeholder. As the ones who find and report defects, and sometimes carry the “quality assurance” moniker, the test community has a unique opportunity to take up the cause of error prevention as a priority. Jeff Payne paints a picture of team and organization-wide quality assurance that is not the process-wonky, touchy, feely QA of the past that no one respects. Rather, it's tirelessly evaluating the software development artifacts beyond code; it’s measuring robustness, reliability, security, and other attributes that focus on product quality rather than process quality; it’s using risk management to drive business decisions around quality; and more. Join Jeff as he explores ways that senior-level test managers and test engineers can lead their organizations—one step at a time—to make incremental progress toward a culture that not only finds defects early but actually prevents them.
Learn more about Jeff Payne
|
|
| |
| |
| |
Elisabeth Hendrickson, Quality Tree Software, Inc.
Teams that succeed with agile methods reliably deliver releasable software at frequent intervals and at a sustainable pace. At the same time, they can readily adapt to the changing needs and requirements of the business. Unfortunately, not all teams are successful in their attempt to transition to agile and, instead, end up with a “frAgile” process. The difference between an agile and a frAgile process is usually in the degree to which the organization embraces the disciplined engineering practices that support agility. Teams that succeed are often the ones adopting specific practices: acceptance test-driven development, automated regression testing, continuous integration, and more. Why do these practices make such a big difference? Elisabeth Hendrickson details essential agile testing practices and explains how they mitigate common project risks related to uncertainty, ambiguity, assumptions, dependencies, and capacity. Join Elisabeth to explore the role of testing and testers in today’s agile development teams.
Learn more about Elisabeth Hendrickson
|
|
| |
| |
| |
Alan Page, Microsoft
What features of your software do customers use the most? What parts of the software do they find frustrating or completely useless? Wouldn’t you like to target these critical areas in your testing? Most organizations get feedback—much later than anyone would like—from customer complaints, product reviews, and online discussion forums. Microsoft employs proactive approaches to gather detailed customer usage data from both beta tests and released products, achieving greater understanding of the experience of its millions of users. Product teams analyze this data to guide improvement efforts, including test planning, throughout the product cycle. Alan Page shares the inner workings of Microsoft’s methods for gathering customer data, including how to know what features are used, when they are used, where crashes are occurring, and when customers are feeling pain. Learn how your organization can employ similar strategies to make better decisions throughout your development life cycle. Alan shares approaches for gathering customer data that can work for any software team —and improve the customer experience for everyone.
Learn more about Alan Page
|
|
| |
| |
| |
James Bach, Satisfice, Inc.
Who drives your career as a tester or test leader? Hopefully, not the company for which you work. It’s you—you must be the driver. Because the craft of testing is still relatively free and open, there is no authority structure that defines or controls our industry. There are no generally accepted and standardized credentials that will admit you to the upper tier of income and respect as a tester. There are no universities that offer degrees in testing—although certificates and certifications abound. What we do have is a pastiche of communities, proprietary methodologies, schools of thought—together with ambitious individuals who write articles, teach, argue with each other, and speak at conferences. James Bach, who has made his own way in his twenty-three year testing career, describes how you can develop your own personal portfolio and reputation to stand out as a senior tester or leader who is indispensable to your current—or any—organization. Join James for an insightful look at what you can do to develop and win your reputation to help your team, project, and company excel.
Learn more about James Bach
|
 |
| |
|
|
| |
| |
Tim Riley, Mozilla Corporation
Open source community-based software development can be extremely wild and woolly. Testing in this environment is even more so, given that it is often less structured than software design and coding activities. What are the differences between testing open source and commercial or corporate applications? What can you learn from the open source community? Take a peek into the open source testing world with Tim Riley as he describes how the Mozilla Project develops and tests the Firefox browser. Tim describes how they monitor new builds, how people all around the world engage in testing, and how anomalies quickly bubble up to the release team. Although some of the tools they use may look familiar, how the Mozilla Project applies them will give you a fresh perspective. Find out how to apply the lessons learned at Mozilla to your projects and unleash the creative power of really smart people inside and outside your organization. Now, more than ever, we need all the help we can get!
Learn more about Tim Riley
|
 |
| |
Top of Page
|
|
|
|
 |
|
|
|
|
