The Latest
|
Six Thinking Hats for Software Testers[presentation] Our testing is only as good as our thinking—and all too often we are hampered by limiting ideas, poor communication, and pre-set roles and responsibilities. |
Julian Harty, Google
|
|
|
STARWEST 2008: Telling Your Exploratory Story[presentation] What do you say when your manager asks, "How did it go today?" As a test manager, you might say, "I'll check to see how many test cases the team executed today." As a tester with a pile of test cases on your desk, you could say, "I ran 40 |
Jon Bach, LexisNexis
|
|
|
Testing Lessons from Springfield-Home of the Simpsons[presentation] Over the years, Rob Sabourin has discovered testing lessons in the Looney Tunes gang, the Great Detectives, and Dr. Seuss. Now he turns his attention to the Simpsons, a primetime cartoon television show entertaining audiences since 1989. |
Robert Sabourin, AmiBug.com Inc
|
|
|
Agile 2008 - Jochen Krebs - Agile PMO, Agile Portfolio Managment, Scrum and More[article]
Podcast
Bob speaks with Jochen Krebs about his portfolio management book and scaling agile. |
||
|
A Word with the Wise: Configuration Management Tips from Steve Berczuk[article] 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[article] 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. |
||
|
Seven Years Later: What the Agile Manifesto Left Out[article]
Video
Brian Marick believes that is partly because the manifesto is focused outwardly; it tells the business how the development team will work with it. Watch Brian’s presentation to find out whether you're really doing agile or if you are agile in name only. |
Brian Marick
December 3, 2008 |
|
|
The Abolition of Ignorance[magazine] 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. |
||
|
Lessons Learned in Close Quarters Combat[magazine] Few would think that the tactics employed by military and law-enforcement Special Forces to breach buildings under siege bears any relation to software project teams. After a number of weekends training with ex-military and ex-law-enforcement Special Forces—just for fun—Antony Marcano draws a surprising parallel between the dynamics of modern Special Forces "room-clearing" methods and the dynamics of modern software development teams. |
||
|
The Key to Good Interviewing[magazine] The foundation of any successful assessment is interviewing a diverse cross section of the staff. But asking the right questions and asking those questions right makes all the difference in the quality of information you can elicit from your interviewees. |
||
 |
Six Thinking Hats for Testers[magazine] 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. |
Julian Harty
November 25, 2008 |
|
What's a Manager to Do?[magazine] 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. |
||
|
A Map by Any Other Name[magazine] A mapping illustrates a relationship between two things. In testing, a map might look like a road map, but it might also look like a list, a chart, a table, or a pile of stories. We can use any of these to help us think about test coverage. |
||
 |
Don't Fear the Repartee[magazine] 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. |
|
 |
Train Wreck Spotting[magazine] An oft-overlooked goal of encapsulation is to simplify usage. Without this sensibility, classes can end up with simplistic interfaces and callers can end up with method-call pile-ups. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.