September 2009
M T W T F S S
« Aug   Oct »
 123456
78910111213
14151617181920
21222324252627
282930  

Software Risks – Some quantification




There are a large number of cases where software development fails to deliver totally, or fails to deliver value upto the required level. This failure has huge economic and human impact, depending on the criticality of the software and its size. We need to find a new way to develop software. The basic problem with software development is risk- a problem that must be solved if the software development process is to be as reliable and as cost effective as other processes like building a house that we can consider to be reliable.

- Dependencies : Some risks arise because of dependencies our project has on outside agencies or factors.
* Customer-furnished items or information.
* Internal and external subcontractor or supplier relationships.
* Inter-component or inter-group dependencies.
* Availability of trained and experienced people.
* Reuse from one project to the next.
- Requirements Issues : Many projects face uncertainty and turmoil around the product’s requirements.
* Lack of a clear product vision.
* Lack of agreement on product requirements.
* Inadequate customer involvement in the requirements process.
* Un-prioritized requirements.
* New market with uncertain needs.
* Rapidly changing requirements.
* Ineffective requirements change management process.
* Inadequate impact analysis of requirements changes.
- Management Issues : Although management shortcomings affect many projects.
* Inadequate planning and task identification.
* Inadequate visibility into project status.
* Unclear project ownership and decision making.
* Unrealistic commitments made, sometimes for the wrong reasons.
* Managers or customers with unrealistic expectations.
* Staff personality conflicts.
- Lack of Knowledge : Software technologies change rapidly and it can be difficult to find suitably skilled staff.
* Lack of training.
* Inadequate understanding of methods, tools,and techniques.
* Insufficient application domain experience.
* New technologies or development methods.
* Ineffective, poorly documented, or ignored processes.
* Technical approaches that might not work.
- Outsourcing : Outsourcing development work to another organization, possibly in another country, poses a whole new set of risks.
* Acquirer’s requirements are vague, ambiguous, incorrect, or incomplete.
* Acquirer does not provide complete and rapid answers to supplier’s questions or requests for information.
* Supplier lacks appropriate software development and management processes.
* Supplier does not deliver components of acceptable quality on contracted schedule.
* Supplier is acquired by another company, has financial difficulties, or goes out of business.
* Supplier makes unachievable promises in order to get the contract.
* Supplier does not provide accurate and timely visibility into actual project status.
* Disputes arise about scope boundaries based on the contract.
* Import/export laws or restrictions pose a problem.
* Limitations in communications, materials shipping, or travel slow the project down.



Leave a Reply

  

  

  

* Copy this password:

* Type or paste password here:

9,761 Spam Comments Blocked so far by Spam Free Wordpress

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>