Skip to main content

Avoiding Half-baked Discovery

Article

Avoiding Half-baked Discovery

Article by Didier Thizy | Comments: (0) | Tue, 07/14/2009 - 1:40pm
Summary:

It can be difficult to explain to your customer why cutting half of the features doesn't cut half of the time and cost. Every software project has fixed costs that often get overlooked in project planning--setting up development environments, ramp-up, building frameworks, and setting up configuration management to name a few. Read on for some ideas on how you can position this with your customer.

"Let's get to the bottom line," said Joe, the potential client, as he put his laptop bag on the boardroom table, just missing the plate of fresh blueberry muffins I'd picked up at my favorite bakery. "I've seen your proposal for adding ten features to the Widget 2.0 application, priced out at $100,000."

My spidey sense went tingly. "You have some changes?"

"We only have $50,000. So we'll take the best five features and call it a deal."

About The Author: Didier Thizy

Didier Thizy is the director of project management at Macadamian Technologies, an Ottawa-based software consultancy with multishore design and development labs. In the past five years, he has led teams to build more than ten new products end to end and is currently overseeing the development of several new projects in the mobile and Web technology spaces. A PMP-certified project manager, Didier's expertise lies in training agile teams in distributed locations. He regularly contributes to the Macadamian monthly column, "The Critical Path," and maintains a blog at softwarepmp.blogspot.com.