Project Management
Better Software Magazine Articles
Use Cases, Ten Years Later Use cases have experienced a long and sometimes rocky history. Look back on the evolution of use cases to better understand how to use them today. |
||
Release Criteria: Is This Software Done? For any project, the big question is: "Is this software ready to release yet?" Explore how to answer that question with confidence, by learning how to define success and how to gain consensus on release criteria. |
||
Karl Wiegers on Humanizing Peer Reviews How serious are you about the quality of your work? Learn how to set aside egos and start benefiting from the experience and perspective of your colleagues. |
Karl E. Wiegers
July 30, 2002 |
|
Becoming Indispensable How can you achieve the lofty status of being an "indispensable" employee? Elisabeth Hendrickson shares some valuable tips, including how to adjust your attitude, where to invest your time, and how to communicate better. |
||
Don't Use Bug Counts to Measure Testers Cem Kaner tells us why we should not use bug counts to measure testers. Using examples, he illustrates two problems: 1) bug counts are poor measures of individual performance; and 2) the side effects of using bug counts as a measure are serious. |
Cem Kaner
July 25, 2002 |
|
Gathering Users for Great Requirements If you buy a hammer, you are not considered a master carpenter automatically. The same holds true for tool knowledge alone solving requirements problems. Kelley Schmidt shares the biggest lesson she learned on a project: commercial process and tools alone cannot lead to project success. |
Kelley Schmidt
July 11, 2002 |
|
Introducing Test-First Development Testers are often frustrated to receive a product for testing that is riddled with bugs. They want to know why some of the bugs couldn't have been caught during development. If only some tests could be run before the code was handed off! Jason Bedunah learned the benefits of test-first development first hand. Here, he introduces a framework for testing and coding that he found to be very helpful, and he gives some pointers on getting developers on board with test-first development. |
Jason L. Bedunah
July 11, 2002 |
|
Women Testing the Waters Picture the faces around the conference table at your last project meeting. How many women were in the room? And how many of them were testers? Alyn Wambeke explores whether the traditionally male-dominated landscape of testing is changing. |
Alyn Wambeke
June 30, 2002 |
|
Breaking the Language Barrier It's wasteful, more often than not, to reinvent the wheel. Christopher Meisenzahl explains how he solved a high-tech automation challenge through the sharing of resources. When faced with similar problems, this sort of collaboration with others may be your most valuable tool—and one that every tester should take advantage of. |
Christopher J. Meisenzahl
June 30, 2002 |
|
Analyzing Requirements Bugs Analysis of bug reports from previous projects tells us about our most frequent errors, and can help us improve. But very few companies spend the time to analyze bugs from completed projects. Otto Vinter and Soren Lauesen explore using bug reports to improve the software development process. |
Søren Lauesen
June 30, 2002 |