Frisking out project risk

Risk Management road sign (Photo credit: Wikipedia)

So what is a risk ? First understands and identify a risk is most important part of risk management.A risk is a probability of uncertainty associated with executing certain item/task/process/work etc. A risk generates out as soon as we initiates a task. A critical resource in terms of skill set, in a team is a potential risk of leaving the project in between because of unavoidable reasons.

So a risk is inevitable, only thing we can do is ; manage and mitigate. Just like handling/catching error in software program. Always plan for the element of risk in project from the start and reiterate control over it for any contingencies.

Steps to assess risk:

Identify---------->Analyze--------------> Set priority to each risk

Steps to control risk:

Mitigate------------>Plan for contingency----------> Quantify it and Set a control process

Design a Solution process at the team level:

Taking help of the experts involved in the project will always a idea for certain of the items to assess for the risk. Prepare a risk register to notify each of the team member and stakeholder.Prepare for ownership records for each of the items .

Comments

Games People Play in context to Projects

Games People Play in context to Projects: Contextually life and projects full of games, work on dynamics of human relationships by Dr. Eric Berne guides us not only in many social but relationship situations in corporate world also. In Todays concurrent world where we are living in a global village with Orkut, Facebook, Linkedin, Twitter and other social media leads to discounts of information in social network, where more of transactional games played knowingly(conscious) or unknowingly(unconscious). Precede to this let us understand game, A game full of transactions played with different roles by players changing their roles for a outcome in different ego states like Parent, Adult and Child ego states that will payoff. Continuing with Payoff, specifically in context to Project teams where transactions happen at concrete or transformational levels where people not necessarily behaving rationally and motivat...

Usecase Scenario development and User Stories

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this: Typical Software Development Life-cycle explained Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development. "A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives. " Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a s...

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of Six Thinking Hats Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming , mischievously known as blame storming. To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits. Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be dis...

Project Portfolio-Program Management

Search This Blog