Geek Answers Handbook

Do you run the risk of analyzing your projects?

Do you use risk analysis techniques when starting new projects?

I like when fresh ppl starts working in a company, they have so much theory that they learn and want to implement when they start working. Risk analysis, project management, coding standards, documentation standards, etc. (Then reality strikes them, most customers will not pay for all this);) But still I really love the fresh winds and the new knowledge that they carry with them!

The automotive industry, and I assume that many other professionals use risk analysis on a daily basis when introducing a new feature or whatever they do.

My experience is that the “risk analysis” I did in the past was to say: “this part is difficult, I don’t know if it will work or not” and “If it does not work, we can try thus".

Today I used the risk analysis protocol related to the automotive industry, and I was impressed that after the meeting he identified one of the most vulnerable projects. And he gave a number of how much attention we should pay to this function in the program against everyone else.

Of course, we did this earlier in projects, but then it was simply called: "What can go wrong in this project" or "What are the obstacles in the project?" is not part of a protocol that can be interrogated between projects and analyzed using nubers.

So, I want to know everything that you know about risk analysis. Light me up!

+5
source share
4 answers

I always analyze risk - both formally and informally (when evaluating, for example, when correcting a mistake).

This is a great tool that allows you to pay due attention to relevant issues, avoid paranoia about some aspects of the project (sometimes we lose perspective and worry about the wrong things) and make difficult decisions when you have limited resources.

It does not have to be extremely formal or time consuming. When you get started, our method will simply ask:

  • "what is the likelihood of this?"
  • "what effect is this happening?"
  • "how much can we deal with this problem?"

1 10 , ( , ).

, ( , : , , )

+2

, . ; - , , , , , , .

Waltzing With Bears: . , .

+2

, :

  • - ,
  • - , .
  • - , ,

, :

  • - , ,
  • . , .
  • - , ( )

, . . . , , . , , , , .

+1
source

Risk analysis is a fancy way of saying “cover my ass when it comes to boobs”, and, as such, is a great way to avoid guilt when things aren't going as planned (which is always a lot in software development).

Risk analysis: indicate everything that may go wrong, write in a good .pdf format and send them to your pointy hair.

-1
source

More articles:


All Articles