The Latest

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.

Technical Editor Brian Lawrence explains his top-three list of things to do to deliver the right software right: risk-based planning, problem definition and modeling, and congruent leadership.

Prototypes can help you deliver the right software. Here, Technical Editor Brian Lawrence gives examples of prototypes and some guidelines for prototyping.

Brian Lawrence and Johanna Rothman recommend Software Requirements by Karl Wiegers, a "readable, practical book about gathering and managing requirements, focused on best practices."

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.

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.

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.