Tomorrow I am going to attend a Risk Management Course in Sofia organized by RammSoft. The course will not only show Risk Management theory but we are going also to participate in a sample project in which we will try to identify the risks, evaluate their probability and after that a discussion on how to avoid them. I love when the practice is much more than the theory, so I am glad that I registered to this course. Also I must also add that I personally know Mike from RammSoft from a long time ago and I am pretty sure that the course will be executed well and will provide me with good value.
What is this risk management about? Risk management is not something new in the area of Software Development Lifecycle process. It is basically trying to identify the possible risks so you can be proactive in the way you manage your project so that eventually you will lower the probability of their occurrence. If after all the risk appears, your decisions taken earlier can isolate the impact of the risk so you do not threaten the whole project. In today’s demands, clients ask for shorter and faster deliveries. In such small time frame, if something delays your project for a week or two, you are in huge trouble. Although small projects are much easier to plan, the risks that may happen in such a short time are often the factors that makes small projects so hard to deliver on time.
Why should you, as a software developer, care about this? There are many risks in a software project that require very deep technical knowledge. It is probably only you in the whole team that is aware of them. Knowing how to handle such issues, or at least how to identify them, will help you do better job and will benefit to the whole team.