The Latest

My Next Mission (And How You Might Benefit from It)[magazine]

Technical Editor Brian Marick proposes organizing a public effort to test a real software product.

Brian Marick
EXtreme Documentation[magazine]

The kind of collaboration that Extreme Programming engenders can benefit both publications and development. Writing, like programming, is a naturally iterative, revisionary process. Dana De Witt Luther shares what she's learned about documenting an Extreme Programming project, using iterative planning meetings and story cards.

Dana De Witt Luther
Interesting Times[magazine]

Technical Editor Brian Lawrence offers some troubling trends he sees in the world of software development and testing, including software produced in "Web Time" and mainline business functions being moved onto Web-based systems.

Brian Lawrence
When Your Manager Is No Techie[magazine]

It's a pretty good bet that at some point in your career you and your work will be managed by someone who doesn't really understand what you do. Here are some ways to close the communication gap when you have a nontechnical manager.

Alyn Wambeke
Measuring Up[magazine]

You measure because you want to make better-informed decisions. But even simple, harmless-looking measures can be dangerous. For example, they can give you a nice, clear picture of an illusion. Do you want to base your decisions on illusions? Technical Editor Brian Lawrence advises that, before you dive into measuring anything, ask yourself, "Will measuring do more harm than good?"

Brian Lawrence
(Management) Process Improvement[magazine]

Few people know intuitively how to manage process, projects, and people. Like anyone else learning a new skill, new managers need training, guidance, and mentoring. And just like technical staff, experienced managers need to keep their skills current and evolve with an evolving workplace. Technical Editor Esther Derby gives advice on how to develop your management abilities.

Esther Derby's picture Esther Derby
The Wonderful World of Software[magazine]

Former STQE magazine Technical Editor Brian Lawrence shares a tale about why a commitment to quality and paying close attention to detail are critical elements in building better software. It’s all about careful planning and anticipating customer behavior. Go with Brian on a stroll through one of the oldest, best-known amusement parks to find out more.

Brian Lawrence
Big Ball of Mud[magazine]

Much of recent systems theory revolves around applying ideal software development patterns. Big Ball of Mud, in contrast, is for those of us who live and work in the real world, where most systems emerge haphazardly from minimally controlled chaos under constrained development conditions. Bar Biszick recommends and describes the Big Ball of Mud Web site.

Bar Biszick
Interviewing Your Interviewer[magazine]

Job interviews are stressful. Often, people are so eager to impress the interviewer that they don't find out critical information about the company and the position. But it's just as important for you to be convinced of the position's suitability for you as it is for the company to be convinced of your suitability for the position. If you ask the right questions, interviews can be much more productive at helping you avoid poorly managed, unhappy projects and zero in on well-run, professional projects.

Joe Yakich
Managers Are Just for Budget Cutting, Right?[magazine]

Luisa Consolini tells us why the managerial side of quality is as important as the technical side. The precepts she imparts are: 1) there is something as bad as not doing testing—not managing it; 2) if you don't manage quality, you won't improve it just by applying some fancy quality techniques; and 3) people are not second to quality.

Luisa Consolini
Book Review: Mastering the Requirements Process[magazine]

Brian Lawrence points to Mastering the Requirements Process as a valuable reference book. The book presents a complete step-by-step method for gathering, modeling, and specifying requirements. Along the way the authors offer easy-to-understand and appropriate examples that nicely illustrate how to apply their techniques.

Brian Lawrence
Welcome to Software Testing and Quality Engineering[magazine]

Technical Editor Brian Marick introduces the first issue of STQE magazine. He says the magazine "is for people who get their hands dirty, whether by writing tests, cranking out code, managing others, or--perhaps the hardest task of all--being the internal QA consultant who has no direct authority but must somehow persuade ten projects with impossible deadlines to think strategically."

Brian Marick
The Ariane 5: A Smashing Success[magazine]

On June 4, 1996, the maiden flight of the Ariane 5 satellite launcher ended spectacularly after only forty seconds, with bits of the $67 billion vehicle and its payload spread over a fairly large part of French Guiana. The report issued July 19 by the International Inquiry Board noted that the fiery crash was due to a "chain of technical events." The details of that particular chain of events are reviewed here.

Les Hatton
What's in a Name?[magazine]

Technical Editor Brian Marick outlines a goal for the magazine and its readers: gradual process improvement, driven by immediate needs.

Brian Marick
How to Survive the Software Swamp[magazine]

For a project to make long-term progress, it must build a platform of basic engineering practices. On this platform are set the ladders of advanced techniques that you select using risk analysis. Properly managed, these processes help you avoid falling back into the swamp whenever the project is under pressure.

Michael Deck

Pages

CMCrossroads is a TechWell community.

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