This presentation covers the basics of setting up Hansoft to manage risks. It is based on proven and tested methods our customers have used to deliver successful projects.
2. A risk is an uncertain future event that, if it
occurs, will have a negative effect on the
project.
For example:
Cost Risks Time Risks Quality Risks
• Currency fluctuations
• Fixed price contracts (sellers)
• Funding risks (interest rates etc.)
• Uncertain estimates
• Uncertain scope
• External dependencies
• Undefined requirements
• Lack of automatic testing
• No access to end users
3. Risk management in Hansoft
Store risks safely in Risk
ledger
(Risk Breakdown Structure)
Overview with Risk
Dashboards
Create your Risk Workflow(s)
Understand context with Risk
Categorization
Collaborate around mitigation
strategies
Update Probability & Impact
Structure Action
Plan
Create Risk Response Plans
Integrate Risk management
with all other planning aspects
4. The Risk ledger
You can either use the ‘QA View’ or the ‘Product
Backlog’ as your risk ledger in Hansoft.
Administrators can rename them.
Find is a convenient way to quickly filter out the
risks you are currently working with.
Custom columns, such as Likelihood, is easily
added by the Main Manager.
Detailed access and restrictions rules can be
added to ensure access policies are followed
5. Create a common Risk Workflow
Transitions can be added to
control different decisions
paths.
The workflow can have
different end states.
Each risk follows a workflow.
These are easily setup by main
managers.
You can have several
workflows for different types of
risks.
The workflow states
have additional options,
such as notifications
and mandatory fields.
6. Group in Risk Categories
▶ For examples:
▸ Technology and quality risks
▹ Unrealistic goals, change of
platform, using new and unproven
technology
▸ Project management risks
▹ Poor allocation of time and
resources, low quality of plan, weak
ledership
▸ Organizational risks
▹ Lack of priorities, unclear financing
and competition from other projects
▸ External risks
▹ Changing regulations, national risks,
weather etc.
7. Add Probability and Impact with Risk Index
The Risk Index is a function column,
automatically being updated when you change
impact or probability.
8. Add mitigation strategy
▶ Example of strategies:
▸ Avoid: Includes changing the project plan to eliminate the risk,
or protect the project from the impact of the risk.
▸ Move: Transfer the risk to a third party, for example an
insurance company.
▸ Lower: Implement activities that lower the probability and/or
impact of the risk.
▸ Accept: Do nothing about the identified risk. There may for
example be a buffer in the plan that will cover the impact of
the risk, or that there is a low probability.
9. Create a Risk Response Plan
This item is living both in the risk ledger and the
plan. Update it here and it will be automatically
updated in the ledger.
This integrates the risk response plan with the
rest of the plan.
This item is linked to the
risk ledger.
This way allows you to
decouple risk
management from risk
mitigation actions.
10. Create a Risk Dashboard
Build the charts with any measures and
dimensions that you need.
Share dashboards easily with stakeholders and
project members.
11. TAKE THE NEXT STEP – TRY HANSOFT!
info@hansoft.com
www.hansoft.com
1 2
Free for up to 9
users with no
time limit.
The first 30 days is
on us if you want to
try Hansoft at scale