|
Solve the Real Problem: A Formula for Sustainable Solutions There is more to software development problem solving than processes and tools. Discover a way to get to the heart of a problem with none of the hacks, shortcuts, and workarounds that have become the industry norm.
|
|
|
Beat the Odds You know that old saying that the best way to schedule software development is to come up with your best guess and divide by three? In this article, Joel Spolsky explains how to take the guesswork out of estimations by simulating schedules and creating probability curves that are more than just a shot in the dark.
|
|
|
The Proof of the Pudding . . . In this month's Test Connection Michael Bolton recounts a valuable lesson he learned early in his testing career: What's the best way to test a product? Use it yourself.
|
|
|
Take a Stand-Yes or No, not Maybe It's happened again. Your boss corners you and pressures you to take on extra work. The additional project gives you more work than you can realistically do, let alone do well. Find out how you can stand up to your boss and work with him to create reasonable priorities for your time without damaging your relationship.
|
|
|
A Box of a Different Color Are there elements of glass box testing and black box testing that overlap and can be helpful to either type of tester? One developer looks at the gray area between black box testers and glass box testers and comes up with some surprising results.
|
|
|
Up the Organization, Redux Certain management principles are enduring and able to cross the boundaries of industry In this month's Technically Speaking, Lee Copeland takes a look at the software development applications of his favorite management book.
|
|
|
Big, Complex, and Tested? Just Say "When": Software Development Using Presenter First Looking to bridge the gap between code and customers? David Crosby and Carl Erickson elaborate on the benefits of an approach called Presenter First, a simple technique that can be repeated as many times as needed to get the job done.
|
|
|
The Power of Three: A Trio of Techniques for Testing Databases Unit tests are meant to demonstrate something only to the developers of the software. Make the best use of testing with databases by taking advantage of these helpful techniques, which demonstrate something to a wider range of interested parties.
|
|
|
The Case of the Missing Fingerprint: Solve the Mystery of Successful End-of-Project Retrospectives Through this tale of a planning spreadsheet and its effect on three different projects, learn the impact a single decision can have on a project--and pick up some helpful tools like fingerprint graphs and project timelines along the way.
|
|
|
One Step Back ... Two Steps Forward A change to code that previously was working may introduce new failures. Testing for regression can catch these failures, find new problems, and identify opportunities to improve your test design.
|
|