I think Software Project Fail so often because.....

Plum	Journals

About this Entry
Posted by: c_plum Original: 4/6/2006 2:43 AM Views: 53 Comments: 0 eProps: 0 Read Comments Post a Comment Back to Your Xanga Site

Thursday, April 06, 2006

I think Software Project Fail so often because.....

Summary from: http://www.codeproject.com/books/SoftwareProjectSecrets2.asp

Software is unique in that its most significant issue is its complexity.

Software is the most abstract product that can be created in a project.
It is uniquely difficult to define a complete set of requirements for software before beginning development.
Software development technologies change faster than other construction technologies.
Most software development technologies are not mature enough to have a set of proven best practices.
Software development has far more technologies, and its technologies have far more complexity than a single individual can hope to gain expertise with.
Expertise with particular software development technologies is very quickly outdated, and therefore most specific skills are learned on the job.
Software development isn't just a process of creating software; it's also a process of learning how to create the software that is best suited for its purpose.
Software development has been automated to a greater degree than other project-based activities.
Unlike other products, software is not constructed, but rather designed into existence.
Software can be modified rapidly, and this pace is expected, but it's better to implement the changes properly.
No software is perfect as first envisioned; it will always require changes to make it best suit its role.

What do you think about the importance of software project management in this aspect?

The importances of Software project management are communication and changes on techology.

Through communication, no matter client or programmer would know there procces of the project and what they need to concert. From programmer, programmer would know the client do not think the project requirement on practical way sometimes, programmer need to use their knowledge to duel with it. From client, client woud know what are the technology limit to their project requirement. If a new technology appear, client would like to use it on the project. However, programmer would tell client that technology cannot implement to the project.

Posted 4/6/2006 2:43 AM - 53 Views - 0 eProps - 0 comments