The Latest

Transform Your Lifecycle-Virtualize the Test Lab[presentation]

Every tester has heard "it works on my machine" from a developer, referring to a defect deemed to be non-reproducible.

Theresa Lanowitz, voke, Inc.
Alternative Testing: Do We Have to Test Like We Always Have?[presentation]

Are the “old ways” always the “best ways” to test? Julian Harty shares his thought-provoking ideas on when traditional testing is-and is not-appropriate and poses alternatives for us to consider.

Julian Harty, Consultant
Building a Successful Test Automation Strategy[presentation]

You have been told repeatedly that test automation is a good thing and that you need to automate your testing. So, how do you know where to start?

Karen Rosengren, IBM Global Services
Take a Chance-Testing Lessons Learned from the Game of MONOPOLY®[presentation]

For years, MONOPOLY® has entertained countless people with the fictional thrill of what it might be like to make a killing in real estate-or to lose your shirt.

Rob Sabourin, AmiBug.com
The Human Side of Testing[presentation]

Software testing is a unique profession.

Thomas McCoy, Department of FaHCSIA
Becoming a Great Tester: Inspiration, Perspiration, and Renewal[presentation]

Three recent and contrasting trends in software development and IT-agile methods, increasing infrastructure complexity, and the requirement to align more closely with business stakeholders-are reshaping testing’s role.

Isabel Evans, Testing Solutions Group Ltd
STARWEST 2010 Keynote: Lightening Strikes the Keynotes[presentation]

Lightning Talks have been a very popular part of many STAR conferences throughout the years.

Lee Copeland, Software Quality Engineering
Test Team Leadership-Yes, There's a Place for It in Agile[presentation]

One of the gravest misconceptions about the agile methodologies isn’t about documentation, teamwork, quality, or productivity. It’s about the role of leadership and management in the adoption and sustained operation of agile practices.

Bob Galen, iContact
You're Either On the Train or On the Tracks: Radical Realities Shaping Our Future[presentation]

Because the number of applications and environments are exploding, the rate of change is increasing exponentially, and the scope of risk has never been wider or deeper.

Linda Hayes, Worksoft, Inc.
Deliver Applications that Meet Business Needs[magazine]

A common mistake made when building applications to meet business needs is not properly defining business requirements from the get-go. Poorly defined requirements compromise the quality of applications and lead to projects that deliver marginal value or fail outright.

Filip Szymanski's picture Filip Szymanski
Simulation Games: A Way to Improve Communication in the Team[article]

One of the hardest daily tasks developers, QA, ScrumMasters, and product owners encounter is effective communication with others. Sound implausible? According to many articles, research, and personal observations, the main cause of project failure is not technology or hardware, but inefficient communication stemming from lack of effective communication between team members, incomplete business analysis, imprecise requirements, and vaguely formulated business objectives.

Monika Konieczny's picture Monika Konieczny
Four Agile Tips to Eliminate Rework in Application Development[article]

Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile.

Filip Szymanski's picture Filip Szymanski
From Red Tape to No Tape: Organizational Misalignment with Agile Values[article]

Charles Suscheck writes that if you’re in an organization that has signs of post-industrial orientation, now is a good time to take a fresh look at your organization’s underlying (and often oblique) belief system.

Charles Suscheck's picture Charles Suscheck
Adapting to Change in Your Agile Strategies[article]

Len Whitmore writes on using agile practices for the development of software. In the ten years since the Agile Manifesto, the agile development domain evolved, as evidenced by such things as the six levels of planning: strategy, release, iteration, daily, and continuous, with strategy appearing to be the least evolved of the planning levels.

Len  Whitmore's picture Len Whitmore
For Project Managers, Agile Is About Asking a Different Question[article]

Daryl Kulak explains that if we don't ask the right question at the beginning of the project, then no matter how well we answer, it won't be helpful. Perhaps the biggest difference between agile and waterfall is the question being asked. The scope of the project and any judgments of progress are related to this very fundamental question.

Daryl  Kulak's picture Daryl Kulak

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.