You're starting a project. You find yourself involved in a project. You're clients are complaining about problems. Do you know what the problem is? Are you addressing the right problem?

In our frenzy to get started on projects and demonstrate to management our value, we often latch onto the first idea that comes our way - either handed down by management or an initial pass that winds up being the mission.

No matter how good your perceived solution, no matter how cool the interface, no matter what reusable - mature - best-in-class - state-of-the-art development technique you apply; if you solve the wrong problem, it is all a monumental waste.

Most of us, regardless of our position, view ourselves as problem solvers. Yet, few of us are grounded in any formal approach to problem solving. We think it's natural to solve problems by knack, by brute force or because "we're good at it."

This discussion addresses the activities involved in problem definition and problem solution. Steve will demonstrate several problem-solving techniques. Through examples and role-playing, we will examine the pros and cons of various problem-solving approaches.

-----------------------

Steve Marcus is a full life-cycle application developer and consultant (and problem-solver) with Marcus Software Designs, Inc. out of Davis, California. Steve has been practicing systems development since 1981. After ten years with Chevron Corporation, Steve started Marcus Software Designs, Inc. MSD specializes in assisting companies in moving to best-in-class methods by providing training, consulting, facilitation, and mentoring services.