|
|
YOUR FEEDBACK
|
TOP MICROSOFT .NET LINKS Tools
Overcome the Frustrating Lack of .NET Deployment Tools
71% of application problems are still found by real users and not by existing tools or testing procedures
By: Dan Garlewicz; Hon Wong
Sep. 24, 2006 12:30 PM
Digg This!
Page 2 of 2
« previous page
ROI Proposition
For example, let's say that an average developer costs $150,000 a year on a fully loaded basis, and you have a 10-person team for an annual headcount cost of $1.5 million. If these developers have to spend 40% of their time troubleshooting production problems (as noted in the Forrester study), you're spending $600,000 a year on production debugging. If you can cut this percentage from 40% to 20%, the savings will be $300,000 a year.
Take for example the same team of 10 developers, which carry a monthly headcount cost of $1.5 million/12 months, or $125,000 a month. If you can shorten the development cycle of a new application by just one month, you'll save $125,000.
The tools can contribute to operational savings by: - Proactively detecting real user performance problems thus preventing a call to the help desk. The reduction in customer service costs could be as much as $200 per incident, assuming that each incident generates four calls and that the cost of handling each call is $50; and - Minimizing the need to assemble cross-functional problem triage team (consisting of development, network, server, administrative, and DBA personnel) by using the suite of tools to automatically triage the problem. The cost of assembling such a triage team could save, for example, five to 10 man-hours per incident and that conservatively translates to $375 to $750 per incident in out-of-pocket expenses (if operations are outsourced at a $75-per-hour billing rate) or opportunity cost. Certainly, delays in time-to-market, bad application performance, broken links, and exceptions lead to lost opportunities and poor user satisfaction. As you know, poor user satisfaction begets lost business for customer-facing applications, and degrades employee productivity for intranet applications or employee portals. These "soft" costs are harder to calculate and perhaps far exceed the "hard" costs stated above. However, since these costs are typically unknown or not measurable at the front of the project, they are rarely budgeted for and greatly reduced the overall ROI of the project. The .NET Framework has been a tremendous boost to application development, but its very success has increased the demands on development and operations. Adopting tools with the right capabilities can meet these demands and unlock the full potential benefits of developing applications in .NET. To achieve the promise of this environment and adjust to the increased complexity of development, implementation, and ongoing operational support, development and operations teams need to fully understand that a paradigm shift is occurring. This shift provides greater capabilities, and the cost is that the business must come to terms with the requirement for increased focus on comprehensive documentation and testing, service management, and operational support. Implementing performance management throughout the software development lifecycle is a critical aspect for managing the quality of service of a .NET application. By implementing a consistent tool, IT can optimize both the development cycle and ongoing operational controls needed to enhance and maintain the service levels the business demands. Page 2 of 2 « previous page
MICROSOFT .NET LATEST STORIES
SUBSCRIBE TO THE WORLD'S MOST POWERFUL NEWSLETTERS SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
|
SYS-CON FEATURED WHITEPAPERS MOST READ THIS WEEK BREAKING NEWS FROM THE WIRES
|
|||||||||||||||||||||||||||||||||||