Comments on: Release Management, Features or Time

By: riedwaan

riedwaan — Thu, 09 Feb 2012 10:28:22 +0000

However in terms of the article, you absolutely right John.

By: riedwaan

riedwaan — Thu, 09 Feb 2012 10:22:37 +0000

I call it gold plating. This usually happens if the client requests the features to be done by date x and there are no negotiations. They going to get the feature on time however, it’s going to be quite buggy. On a project im working on, this is impossible as the client views unit tests report (using storyq – http://storyq.codeplex.com/) on TFS, so no goldplating.

By: jsonmez

jsonmez — Tue, 21 Sep 2010 17:01:25 +0000

In reply to sander.

You are correct, but let me ask you this question. When you promise them x features by y date, are you just blowing smoke?
The reality of the situation is that you are either lying or padding when you promise to deliver a set number of features in a set number of time.
My recommendation would be to explain this simple truth to your client, and let me know that even if vendor xyz makes that promise, that doesn’t mean they can deliver, but…
What you can do is update them every week so they can get a real time feel for how fast features are being completed and you and have the most realistic projection at any time of when x number of features will be done. A projection based on real data, not WAGS, and one that is updated constantly.

By: sander

sander — Tue, 21 Sep 2010 14:46:51 +0000

I like the idea. But how do i sell it to my clients? One is: Ok, we agree on which features you get, but i can’t say when. Or: Ok you will have some of the features agreed dat, but i can’t tell which. Will be a tough job selling…

By: jsonmez

jsonmez — Tue, 22 Jun 2010 13:18:30 +0000

In reply to Sandbox. Unfortunately it is not just offshore team managers that think that way.

By: Sandbox

Sandbox — Tue, 22 Jun 2010 09:49:44 +0000

John, I completely agree with the philosophy that it is either time or feature, not both. But, it doesn’t quite seem to work with offshore teams. Managers in offshore believe that features need to be delivered, irrespective of time lines. And hence quality sometimes suffers when the development is done by the offshore team.

By: Joe Green

Joe Green — Mon, 14 Jun 2010 17:46:59 +0000

“Padding” indeed is a four letter word in software development. I have seen first hand its corrosive powers work against teams. One thing you didn’t mention is the danger to the developer when enganged in padding. I know we are all perfect, so hypothetically speaking, what happens when we wait till the last second to cross the finish line and then trip on our shoelaces?