Conference Presentations

Moving to an Agile Testing Environment: What Went Right, What Went Wrong

About a year ago, Ray Arell called his software staff together and declared, "Hey! We are going agile!" Ray read an agile project management book on a long flight to India, and, like all good reactionary development managers, he was sold! Now-two years later-their agile/Scrum process has taken shape; however, its adoption was not without strain on development, test, and other QA practices. Join Ray as he takes you on a retrospective of what went right and, more importantly, what went wrong as they evolved to a new development/test process. He introduces the software validation strategies developed and adapted for Scrum, explains what makes up a flexible validation plan, and discusses their iterative test method. Learn how they use customer personas to help test teams understand expectations for quality in each sprint and employ exploratory testing in the Scrum development flow.

Ray Arell, Intel Corporation
STARWEST 2009: The Marine Corps Principles of Leadership

Even with the best tools and processes in the world, if your staff is not focused and productive, your testing efforts will be weak and ineffective and your finished product will reflect this. Retired Marine Colonel, long-time test consultant Rick Craig describes how using the Marine Corps Principles of Leadership will help you become a better leader and, as a result, a better test manager or tester. Learn the differences between leadership and management and how they can complement each other. Discover new approaches to energize your testers and learn to avoid some that won't. Rick explores motivation, morale, training, span of control, immersion time, and how to promote a consistent testing discipline within your organization. He addresses the role of "influence leaders" and how to use them as powerful agents of change.

Rick Craig, Software Quality Engineering
Par for the Course

What can happen over a game of golf? You learn what you don't know, you learn more about what you do know, and you learn to listen to what others know. See how two managers and a caddy team up for some valuable lessons about staying out of the rough.

Patrick Bailey's picture Patrick Bailey
Outside the Strike Zone

In a counterpoint to his previous Technically Speaking column, Lee explains why holding fast to one's beliefs is not necessarily a bad thing.

Lee Copeland's picture Lee Copeland
Countdown to Agility

Jean Tabaka believes in the power of an entire agile organization. These ten characteristics of an agile organization may seem counter to market success, but she explores why they are wholly embedded in twenty-first century business success.

Jean Tabaka's picture Jean Tabaka
To SME or Not To SME

Subject matter experts (SMEs) serve important roles on a project and are especially pivotal during the testing phase. In this week's column, Dion Johnson explores how SMEs positively and negatively affect testing and what you can do to make sure you have the right amount of SMEs on your testing team.

Dion Johnson's picture Dion Johnson
Project Time Reporting

Project time reporting evokes a passionate response from most team members-- the consensus is they hate it. While Payson Hall worries about supporting something so unpopular, he offers benefits of project time reporting and explores some of the common implementation issues that undermine its value.

Payson Hall's picture Payson Hall
Rocks into Gold: Part 2

This short book, written by Clarke Ching, is a "biztech" parable for software developers who want to survive—and then thrive—through a credit crunch. We have republished the book in a four-part series. In part two, Bob, Bill, and Sam discover how a rocky economy can flip project costs and return on investments and how much money could be lost by canning the FBU project. Can they use these projections to save the project and their jobs?

Clarke Ching's picture Clarke Ching
It Takes a Village

Pair programming is an Agile practice that has been shown to greatly improve code quality without a huge increase in development time. This article explains the ins and outs of pair programming and some things you need to consider before you tell team members to grab a partner and get programming.

Ronica Roth's picture Ronica Roth
The Whos and Wheres of Stakeholder Requirements

Whether you're working on a collocated or a distributed team, it's important to take stakeholder requirements into account: "Who" are they and "where" are they located? In this article, Mary Gorman offers some tips to help you narrow the gap between thinking and acting globally and locally.

Mary Gorman's picture Mary Gorman

Pages

AgileConnection is a TechWell community.

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