What is the best way to analyze project risk?

Question

Is there any way to avoid project related errors? And is it different from the type of projects you are working on (for example: website, client / server ...)?

Answer 1

"Does [risk] differ depending on the type of projects you are working on?"

Yes, absolutely. There are several universal risks for software projects (lack of managerial obligations, poor communication, etc.), but the risk profiles differ in context. The risks of a video game project, say, are very different from the risks associated with an enterprise supply chain project.

, , , , , .

, , , " " .

( , , ...). , , , .

- " " .

Answer 2

. . , , :

Software Survival Guide Steve McConnell ( , )

alt text http://ecx.images-amazon.com/images/I/41X9bGinoNL._SL500_BO2,204,203,200_AA219_PIsitb-sticker-dp-arrow,TopRight,-24,-23_SH20_OU01_.jpg

Answer 3

- - , .

, , . " ", , , , " ". , , , , , , , .

, , , , , . , , , . , " ", , , .

The Mythical Man-Month Fred Brooks .

Answer 4

- , , , stackoverflow. ( Software Project Survivial Guide - ) .

Answer 5

:

, , , ( , " " ). , , .

, NASA ( "" !) Quality Quality Models. IBM .

.

, ( "release" ), "" .

Answer 6

. , .

Answer 7

: Software Design (PDF), , , , , ...

Answer 8

A couple of key risks include: Do programmers know what to build, and how to do it, and can they work together? Some development methodologies, including flexible and extreme ones, attack these risks, forcing to create something real as quickly as possible, and then developing a working system, moving one high-priority business goal at a time.