![]() |
A Detour Around Dead-end Bugs Show-stopping failures in Web applications are all too common. One serious but easily avoidable failure is the "dead-end" bug, where a user is left staring at a blank screen without any clue about what went wrong. Derek Sisson describes different types of "dead-end" bugs and shows how to avoid them. |
Derek Sisson
June 26, 2002 |
Software Requirements Brian Lawrence and Johanna Rothman recommend Software Requirements by Karl Wiegers, a "readable, practical book about gathering and managing requirements, focused on best practices." |
||
![]() |
EXtreme Documentation 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
June 26, 2002 |
When Your Manager Is No Techie 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
June 26, 2002 |
|
(Management) Process Improvement 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. |
||
Reference Point: The Software Project Manager's Handbook The Software Project Manager's Handbook is an excellent reference for the experienced or moderately experienced project managers who are looking to expand their "bag of tricks." Use this book as a reference to bone up on a specific topic, or use the case studies and questions to help you design and implement a feasible project plan. |
Maureen A. O’Hara
June 26, 2002 |
|
![]() |
Making Numbers Count Numbers count—no two ways about it. But any numbers you include in a bug report should also include the appropriate units of measure. In an example from their experience, David Wilson and Leonidas Hepis explain the importance of using consistent terminology and units of measure. |
|
A Cautionary Tale Technical Editor Brian Marick uses a fairy tale format to warn software professionals against using easy-to-acquire numbers in place of human judgment. |
Brian Marick
June 26, 2002 |
|
My Next Mission (And How You Might Benefit from It) Technical Editor Brian Marick proposes organizing a public effort to test a real software product. |
Brian Marick
June 26, 2002 |
|
Interesting Times 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
June 26, 2002 |
Pages
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |