Risk Management in Systems/Software Development

I have been commissioned by the City of Tayabas to manage the computerization of various systems of the local government unit. Part of managing the project is constant reporting to the project champion and I have been asked to deal with the risks that may occur.

Since risks in software development is inevitable, I have here basic guidelines that you might consider of using.

First thing to do is to assess. Enumerate the risks according to the probability of occurence. Rank them from the most to least dangerous taking into consideration of its possibility to happen.

Second is to control. Make another list on how to mitigate and probably control these risks. There must be a sound strategy. Come up with a technique appropriate to the identified risks and implement it accordingly.

Common risks are as follows;

1. Technical personnel shortfalls and uncooperative users.
2. Schedules and budgets.
3. Continuing stream of requirements changes. This is the old requirements creeping syndrome.
4. Developing incorrect user interfaces, functions and properties.
5. Gold plating. This is where the project team add functionalities and features to the product which is not called for.

I will be posting thourough discussions on this topic in qtechbpo.com website.

All set and ready

Now everything is set and ready. I have the visitor's counter, google adsense and some useful gadgets. Why I did this? I will "walk the talk", "preach what I teach".

For qtechbpo.com team, the buzz is always SEO and let us start from here. This will be the criteria, your reaction either violent or otherwise is welcome.

Most number of hits : 20%
Highest earnings from Google adsense : 20%
Most number of comments : 20%
Most number of posts: 20%
Google ranking : 20% (using these keywords: qtech bpo, quezon, lucena, tayabas, business process outsourcing)

Should the given criteria is not acceptable, post your comment here. :)

Ciao!