The Latest

Improve Your Testing with Static Analysis[presentation]

Static analysis is a technique for finding defects in code without executing it. Static analysis tools are easy to use because no test cases are required. In addition, today's technology has advanced significantly over the last few years.

Paul Anderson, GrammaTech
The Marine Corps Principles of Leadership[presentation]

Even if you have the best tools and processes in the world, if your staff is not motivated and productive, your testing efforts will be weak and ineffective.

Rick Craig, Software Quality Engineering
Improve Your Testing through Automation[presentation]

Are you wondering how to increase progress with your test automation efforts? Do you understand how to measure the efficiency and effectiveness of your automation activities?

Jim Sartain, Adobe Systems
Beyond Testing: Becoming Part of the Innovation Machine[presentation]

Testing, once a marginalized function at Google, is now an integral part of Google's innovation machine. Patrick Copeland describes how this vital transformation took place.

Patrick (Pat) Copeland, Google
Crossing the Chasm: Agile Transitions for Test Teams[presentation]

Even if agile development has "crossed the chasm" and is becoming a mainstream set of practices, testers are often left behind when development teams "go agile." Developers learn test-driven development, continuous integration, refactoring, p

Janet Gregory, DragonFire Inc.
What Haven't You Noticed Lately? Building Awareness in Testers[presentation]

"What haven't you noticed lately?" Marshall McLuhan is said to have asked this paradoxical question-a vital one for testers, because it prompts more questions about things that testers could and should notice.

Michael Bolton, DevelopSense
The Testing Dashboard: Becoming and Information Provider[presentation]

Primary concerns for test managers are keeping the testing on schedule, meeting test objectives, making sure tests are effective, and satisfying stakeholders.

Randy Rice, Rice Consulting Services
What's More Important: Being Agile or Creating Value?[article]

In this video, Jonathan Kohl looks at why and for whom we develop software, what our end users and team members value, and the difference between tools and processes that create value and those that distract from it.

Jonathan Kohl's picture Jonathan Kohl
Performing the Software: Succeeding at Agile Development[article]

Sometimes, it's helpful to explore how people in other occupations create their products in order for us to better our own. In addition to being an experienced software tester, Chris McMahon has spent time on the road and in the studio as a professional musician. In this article, Chris takes a look at some of the things that make for a successful live concert and compares them to what it takes for an agile team to build software successfully.

Chris McMahon's picture Chris McMahon
No: Such a Difficult Word[article]

When people begin to get overworked, it's common to fall back on blaming the old chestnut "time management." But the problem may have less to do with how you allocate time to projects than your inability to say no to some of those projects in the first place. In this article, Johanna Rothman takes a look at the difficulty of saying no and offers some suggestions for overcoming it.

Johanna Rothman's picture Johanna Rothman
Tips and Advice - Continuous Integration[article]
Podcast

Tips and Advice - Continuous Integration

Bob Payne's picture Bob Payne
How Agile Practices Reduce the Top 5 Requirements Risks[magazine]

Requirements risks are among the most insidious risks threatening software projects. Whether it is having unclear requirements, lack of customer involvement in requirements development, or defective requirements, these troubles are a major culprit in projects that go awry. As requirements expert and agile coach Ellen Gottesdiener explains, agile practice can go a long way in mitigating the top five requirements risks.

Ellen Gottesdiener's picture Ellen Gottesdiener
Adapting Inspections to the Twenty-first Century[magazine]

How do you adapt inspections to a twenty-first century distributed workforce? A key part of the inspection process is the team meeting, which provides peer pressure to participate and consensus on defects. Teams working in multiple time zones have limited opportunities for the team meeting. A list of requirements and the functions needed to solve this problem based on real-world experiences should help anyone faced with this problem.

Ed Weller's picture Ed Weller
Predicting the Past[magazine]

Developing an accurate prediction process is complex, time consuming, and difficult. But, basing predictions on causality rather than correlation and learning how to "predict the past" can help us gain confidence in the validity of our work.

Lee Copeland's picture Lee Copeland
That's No Reason to Automate![magazine]

Automating test execution is supposed to give tremendous benefits, but often gives disappointing results—because it hasn’t met the objectives set for it. The fault may not lie with the automation itself, but with the objectives you are attempting to achieve. Aiming at the wrong target does not bring success! For example, objectives for automation are often confused with objectives for testing, but they should be different. In this article, learn how to avoid the most insidious traps and how to recognize good objectives for automation.

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!