Group Actions
Engagement
  • Author Author: jamesbenson
  • Date Created: Date Created
  • Views 678 views
  • Likes 1 like
  • Comments 2 comments
Related
Recommended

....And the kitchen sink!

jamesbenson

Early in my consultancy, I was eager to please. First clients aren't easy to find! But this particular client was working on a new microcontroller implementation of an existing product. It started as a simple way to control the system, but as opportunities for project improvements came up everything became something that should be added. Some of the extra features were:image

  • The ability to log system diagnostic data
  • The ability to log user input data
  • The ability to support USB communication to get the data off
  • A change from simple LED on/off to blinking, fading, pulsing LEDs

Not wanting to say, 'no' or tell my client that their project management would result in schedule and cost explosions, I complied with all requests with a measly warning of the delays. In the end, the project had to be shelved all together based on budget constraints. I understand now that the project is re-designed slightly and reverted back to not even using a microcontroller! It was a self-management lesson for me as well: bad news is worse when not bought out into the open.

 

It's no wonder that the management that couldn't keep an eye on their spec 'budget' had a hard time managing the finances....

  • in reply to Workshopshed

    You're right to mention the risks involved with hardware. While spinning a new PCB isn't awful (an usually happens a few times before release of the design), there can be real trouble when asking the mechanical engineer on thee theam to add space to his case to accommodate a slightly larger PCB. The answer is often times 'No.' But my story above describes the other side of the spectrum....

  • There's a principle of "Extreme Programming" called YAGNI or "You arn't going to need it". The idea is that you should avoid adding functionality early as it will impede development and if it's needed it can be added later.

    I wonder if this can be applied to hardware too or if the cost of change makes that approach equally unworkable.