Thoughts from the trench - by Prakash Muralidharan

August 19, 2008

Nederlands/Dutch Français/French ???????/Russian Deutsch/German Italiano/Italian Português/Portuguese Español/Spanish ????????/Greek 日本語/Japanese 한국어/Korean 中文(简体)/Chinese Simplified 中文(简体)/Chinese Traditional

Weakest link in software development ?

Filed under: Software Services, Project Management, Program Management — Prakash Muralidharan @ 1:53 am

Abhijit writes about estimation as being the weakest link in software development. He says:

"Most of the times the people who estimate and people who develop are different, their skillsets are different, and most importantly the business needs and constraints change at a higher frequency. "

Estimation is surely a weak link. Often, sales guys try to sell the project through an estimate. From a management perspective, if you can get the three edges (scope, time, cost) of the 'golden' triangle to meet then you have a successful development project. What do you think is the weakest link ?

View Results


Linking and Sharing

If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Weakest link in software development ?

del.icio.us:Weakest link in software development ?  digg:Weakest link in software development ?  fark:Weakest link in software development ?
Trackback

Trackback URI for this entry:

http://www.prakashonsoftware.org/blog/index.php/2008/08/19/weakest-link-in-software-development/trackback/

No Comments »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a comment

Creative Commons LicenseDisclaimer : This blog site is published by and reflects the personal views of Prakash Muralidharan,in his individual capacity. It does not necessarily represent the views of any of his employers, past or present, and is not sponsored or endorsed by any of them. No representation is made about the accuracy of the information contained in this blog.