Geeks With Blogs

Tim Murphy

Tim is a Solutions Architect for PSC Group, LLC. He has been an IT consultant since 1999 specializing in Microsoft technologies. Along with running the Chicago Information Technology Architects Group and speaking on Microsoft and architecture topics he was also contributing author on "The Definitive Guide to the Microsoft Enterprise Library".

I review for the O'Reilly Blogger Review Program

Technorati Profile

Tim Murphy's .NET Software Architecture Blog Adventures in Architecting and Developing .NET

Managing a software development project is always a risk versus benefit balancing act.  It seems that lately the scales have tipped way over to the side of reducing risk rather than supplying benefit. 

What do you do when you have a problem with an application but a fix won't be allowed because there is a work around?  The benefit needs to be put into terms of savings.  Does the solution require regular intervention on the part of a support team or is the user delayed in their work while waiting for the work around to be executed?  These are factors that have a cost.

In the end it may still be determined that the cost of a work around is less than the benefit of a new feature or fixing a different problem.  Remember though that it is always worth making decision makers aware of the real cost of something not being fixed.  This can cause the risk associated to be accepted because the benefit is more clearly stated.


Posted on Thursday, January 24, 2008 12:03 PM Development | Back to top

Comments on this post: Risk Aversion In Software Development

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Tim Murphy | Powered by: | Join free