Do you think that agile project management suits software development more than traditional project management

State the reasons!!!! plz help me

Do you think that agile project management suits software development more than traditional project management
I think a lot of it depends on the type of project and the procurement process. For example, the US Federal government has procurement processes it must, by law, follow for software acquisition. Those processes don't necessarily accommodate changes in software development practices. So while the S/W engineers and managers may want to follow an agile process, they may have deliverables required by the contract that are products of a more traditional management process.





Likewise, if the software product being developed has other "external" requirements - like human safety, or security, robustness, etc. - proving that you have met those requirements may require development artifacts that are not part of the agile process. Whether or not you met those requirements in the agile process is not so much the question, as to what artifacts did your process generate that documents that the requirements were met.





My philosophy is "things are the way they are for a reason." So if agile processes want to dispense with things like documentation, design reviews, etc., you need to understand why those things were part of a traditional process, and to decide what you are losing by doing away with them.