|
Has the Time for the Adversarial Organization Passed? The concept of an independent test organization is considered a "best practice" by many experts in the industry. Is this degree of autonomy actually a good thing in the real world today? In such a structure, some testers can only play "Battleship" with the delivered software, shouting gleefully when they find a defect. On their first tours of Toyota's factories, American automakers were astonished to find no "rework area." Toyota engineers didn't subscribe to the approach of inserting defects on the production line only to remove them later in the quality control and rework area. Yet this is exactly what the independent test group excels at! Is it time to discard this organizational model and focus on working together with developers to prevent defects in the first place? Gerard Meszaros examines the sacred concept of independent test teams based on experiences from the agile software movement and Lean production systems.
|
Gerard Meszaros, Independent Consultant
|
|
A Word with the Wise: Configuration Management Tips from Steve Berczuk In this short interview with editor Joey McAllister, Steve Berczuk offers some tips to organizations dealing with configuration management (CM) issues.
|
|
|
Transitioning from Analysis to Design The step between specifying requirements to working on a system design can be tricky. Fortunately, the basis on which the step is made can be calculated. Paul Reed thoroughly explains how the transition should progress and offers some instructions on how to move properly through this phase.
|
|
|
The Abolition of Ignorance The testing profession isn't easily mastered, and isn't something that can be perfected by practice alone. Good testers study testing to improve their knowledge of the areas they know about, but great testers strive to find out about areas of software testing they don't yet realize they don't know about.
|
|
|
Six Thinking Hats for Testers Fresh ideas can provoke us into discovering great insights: Six thinking hats did just that for Julian Harty, who then applied them to software testing with great success. He, and tens of others, has found the thinking hats easy to use, practical, and very productive. Read on to find out how you can apply them to your work.
|
|
|
What's a Manager to Do? Self-organizing teams still need managers. But those managers need to rethink how they do their jobs and consider how much self-management the team can take on. Finding the sweet spot between hands on and hands off is the key.
|
|
|
Don't Fear the Repartee Conflict reduces people's productivity and generosity toward the organization and their coworkers. These four steps can help defuse a conflict situation and improve the chances for a solution that at the least, both parties can live with.
|
|
|
Simple Strategies to Keep Quality Visible In most projects, testers are the keepers of quality. Sharing the vision of quality with the entire team helps everyone involved in a project play a more active role in determining the state of quality in a product. In this column, Jeff Patton shares several innovative ideas he's seen in practice lately that have helped an entire team own up to the quality of its software.
|
|
|
Relearning to Program Twenty years ago, Clarke Ching fell in love with programming. Then he got a job doing just that and fell out of love within five years. Fifteen years later, Clarke sought the help of a well-known programmer for advice on how to rekindle his dormant passion for programming. The advice Clarke received led to a greater discovery.
|
|
|
Five Tips for Retrospective Leaders and Meeting Moderators Before you schedule or moderate another retrospective meeting, read this column by Esther Derby. Esther offers five tips that will help improve the productiveness of retrospective meetings. You'll also learn how letting the meeting participants run the conversation will solicit more feedback and ownership than traditional moderation methods.
|
|