Breaking News
Comments
Newest First | Oldest First | Threaded View
Page 1 / 2   >   >>
RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:52:27 PM
NO RATINGS
Hi Frank, Using transistors to measure design complexity is wholly inaccurate -- I couldn't agree more. I wrote an article on how my firm does it, which is a production-proven approach applied to several thousand IC projects. Here's the URL http://www.eetimes.com/electronics-blogs/other/4210492/How-complex-is-your-chip-design-

RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:46:27 PM
NO RATINGS
Productivity indeed is a function of skillset, corss functional teams, etc. (e.g. tools, methodolog and management). Not sure what you mean by hard rules. Benchmarking is NOT subjective -- my firm has been doing it for over 15 years on over 3,000 IC and embedded SW projects.

RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:43:04 PM
NO RATINGS
Wrong. Productivity will consistely decline as team size increases. I think what you meant to say is that increasing manpower by 10X will not result in a 10X increase in throughput. That's absolutely correct. The increase depends on the quality of the management of the team (and organization and company). The name of the game is to minimize the decline in productivity as team size increases.

RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:39:10 PM
NO RATINGS
Please elaborate.

RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:38:24 PM
NO RATINGS
Precisely. Thanks for your comment. RC

RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:37:09 PM
NO RATINGS
Mythical man month is alive and well -- to a point. Adding people does not increase througput linearly, but it does increase it. The issue is determining the point of diminishing returns. But most R&D organizations don't get bogged down in such questions, because lack of resources does not give them the luxury to think about the possibility of adding too many engineers to a project.

RCollett
User Rank
Author
re: Why they benchmark productivity
RCollett   4/26/2012 11:33:32 PM
NO RATINGS
Nimrod, 1. It is irrefutable that larger project teams have higher throughput than smaller teams -- but there is certainly a law of diminishing returns. I have observed this first hand on hundreds of projects. 2. Adding people in the middle of a project, as opposed to at the outset, may or may not increase throughput. It really depends on the particular project and situation. In most cases it will, but the impact could easily be minimal. Again, depends on the project/situation. 3. Engineering resources are not fungible. Not sure why you think the article implies they are. 4. Across the industry companies are increasing team sizes because the rise in design complexity is outstripping productivity improvement. Again, irrefutable fact -- based on data.

t.alex
User Rank
Author
re: Why they benchmark productivity
t.alex   4/21/2012 3:52:16 AM
NO RATINGS
Seems the author does not bother to respond..

old account Frank Eory
User Rank
Author
re: Why they benchmark productivity
old account Frank Eory   4/19/2012 10:25:45 PM
NO RATINGS
Be careful what you measure and how the measurement incentivizes or disincentivizes your engineers. I remember many years ago a project in which management decided lots of productivity metrics should be collected. For IC designers, the metric was transistors per hour, much as for software engineers it was lines of code per hour. Heaven help you if you were doing RFIC design, where your entire design is a relatively small number of transistors! But for us digital guys, especially those of us with a lot of DSP/datapath content, the metric was hilarious. Watch me code up tens of thousands of transistors in seconds: wire [31:0] x, y; wire [63:0] z; always @ (x or y) z = x * y; Voila! A 32x32 bit multiplier in about 15 seconds. Ok, I haven't synthesized it yet, but synthesis will complete in less time than it takes me to go get a cup of coffee. Since DSP designs require many multiply and add operations, I can blow up the die size in no time by dropping down hardware multipliers every time an algorithm requires a multiplication. Yeah, but we all know that's not the optimum way to architect an algorithm-on-silicon. But hey, look at my transistors per hour metric! In the words of one of my favorite Dilbert cartoons from years ago, in which financial incentives were tied to productivity metrics: "I'm going to code me a new minivan!"

t.alex
User Rank
Author
re: Why they benchmark productivity
t.alex   4/18/2012 11:39:34 AM
NO RATINGS
Sometimes the productivity comes from more complex factors such as skillset, cohesion of cross functional teams, etc. There are no hard rules for this, and of course benchmarking or measuring is very subjective right?

Page 1 / 2   >   >>


Radio
LATEST ARCHIVED BROADCAST

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.

Brought to you by:

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Like Us on Facebook
Special Video Section
With design sizes expected to increase by 5X through 2020, ...
01:48
Linear Technology’s LT8330 and LT8331, two Low Quiescent ...
The quality and reliability of Mill-Max's two-piece ...
LED lighting is an important feature in today’s and future ...
05:27
The LT8602 has two high voltage buck regulators with an ...
05:18
Silego Technology’s highly versatile Mixed-signal GreenPAK ...
The quality and reliability of Mill-Max's two-piece ...
01:34
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...
The LT®6375 is a unity-gain difference amplifier which ...
The LTC®4015 is a complete synchronous buck controller/ ...
10:35
The LTC®2983 measures a wide variety of temperature sensors ...
The LTC®3886 is a dual PolyPhase DC/DC synchronous ...