Risk Management in Sprint Environment
-
Upload
mike-wienold -
Category
Software
-
view
55 -
download
0
Transcript of Risk Management in Sprint Environment
IEE Risk IdentificationTask-level Risk for Sprint Planning
Nov 19 2013
RISK MANAGEMENT
raquo Purpose Add risk planning to the sprint planning meetings
raquo This deck includes
bull Refresher of risk management process
bull Understand steps necessary for risk planning at the task-level
bull Understand how to create and write a risk
bull Define mitigation vs contingency plans
bull Identify expectations for tracking and monitoring
Sprint Planning
RISK DEFINITION
raquo What is risk
bull Risk is exposure to a problem an uncertain event that if occurs will
impact the success of the project (functionality cost schedule etc)
raquo Whatrsquos the difference between risk and an issue
bull Risk is unknown and an issue is known An issue may result from
risk andor create new risk
raquo If lsquouncertainty Xrsquo happens lsquoimpact Yrsquo will result
RISK MANAGEMENT PROCESSTask Level for Sprint Planning
Perform Risk
Identification
Perform Risk
Analysis
Plan Risk
Response
Monitor and
Control RisksClose Risks
Review Risk
Areas
Identify
Potential Risks
Write Risk
Statements
Analyze List of
Risk
Statements
Identify Risks
to Track
Enter Risks in
TFS
Complete
Description amp
Data
Plan
Mitigation
Create tasks
ID Triggers
Plan
Contingencies
Execute
Mitigation
Tasks
Communicate
with Team
Track Changes
in TFS
Triggers
Expired
Tasks
Completed
Breakdowns
Resolved
Score
Probability amp
Impact
Breakdowns
Trigger
Contingencies
Record
Lessons
Learned
CATEGORIES OF RISKFocus of Task Risks Release
Project
Technical
Technology
Integration
Performance
Quality
External
Vendors
Regulations
Market
Customer
Org
Dependencies
Resources
Budget
Priority
Proj Mgmt
Estimates
Plan
Control
Communication
Requirements
Experience
Mgmt Advocacy
Process
Schedule
RISK OWNERS
raquo External and Business Risks PLM Directors Sales
raquo Organizational Risks Directors Managers
raquo Project Management Risks Project Managers Managers
raquo PBI Risks Product Owners Sprint Teams
raquo Tasks Risks Sprint Teams
PBIsTasks are Focus of Sprint Teams
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
RISK MANAGEMENT
raquo Purpose Add risk planning to the sprint planning meetings
raquo This deck includes
bull Refresher of risk management process
bull Understand steps necessary for risk planning at the task-level
bull Understand how to create and write a risk
bull Define mitigation vs contingency plans
bull Identify expectations for tracking and monitoring
Sprint Planning
RISK DEFINITION
raquo What is risk
bull Risk is exposure to a problem an uncertain event that if occurs will
impact the success of the project (functionality cost schedule etc)
raquo Whatrsquos the difference between risk and an issue
bull Risk is unknown and an issue is known An issue may result from
risk andor create new risk
raquo If lsquouncertainty Xrsquo happens lsquoimpact Yrsquo will result
RISK MANAGEMENT PROCESSTask Level for Sprint Planning
Perform Risk
Identification
Perform Risk
Analysis
Plan Risk
Response
Monitor and
Control RisksClose Risks
Review Risk
Areas
Identify
Potential Risks
Write Risk
Statements
Analyze List of
Risk
Statements
Identify Risks
to Track
Enter Risks in
TFS
Complete
Description amp
Data
Plan
Mitigation
Create tasks
ID Triggers
Plan
Contingencies
Execute
Mitigation
Tasks
Communicate
with Team
Track Changes
in TFS
Triggers
Expired
Tasks
Completed
Breakdowns
Resolved
Score
Probability amp
Impact
Breakdowns
Trigger
Contingencies
Record
Lessons
Learned
CATEGORIES OF RISKFocus of Task Risks Release
Project
Technical
Technology
Integration
Performance
Quality
External
Vendors
Regulations
Market
Customer
Org
Dependencies
Resources
Budget
Priority
Proj Mgmt
Estimates
Plan
Control
Communication
Requirements
Experience
Mgmt Advocacy
Process
Schedule
RISK OWNERS
raquo External and Business Risks PLM Directors Sales
raquo Organizational Risks Directors Managers
raquo Project Management Risks Project Managers Managers
raquo PBI Risks Product Owners Sprint Teams
raquo Tasks Risks Sprint Teams
PBIsTasks are Focus of Sprint Teams
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
RISK DEFINITION
raquo What is risk
bull Risk is exposure to a problem an uncertain event that if occurs will
impact the success of the project (functionality cost schedule etc)
raquo Whatrsquos the difference between risk and an issue
bull Risk is unknown and an issue is known An issue may result from
risk andor create new risk
raquo If lsquouncertainty Xrsquo happens lsquoimpact Yrsquo will result
RISK MANAGEMENT PROCESSTask Level for Sprint Planning
Perform Risk
Identification
Perform Risk
Analysis
Plan Risk
Response
Monitor and
Control RisksClose Risks
Review Risk
Areas
Identify
Potential Risks
Write Risk
Statements
Analyze List of
Risk
Statements
Identify Risks
to Track
Enter Risks in
TFS
Complete
Description amp
Data
Plan
Mitigation
Create tasks
ID Triggers
Plan
Contingencies
Execute
Mitigation
Tasks
Communicate
with Team
Track Changes
in TFS
Triggers
Expired
Tasks
Completed
Breakdowns
Resolved
Score
Probability amp
Impact
Breakdowns
Trigger
Contingencies
Record
Lessons
Learned
CATEGORIES OF RISKFocus of Task Risks Release
Project
Technical
Technology
Integration
Performance
Quality
External
Vendors
Regulations
Market
Customer
Org
Dependencies
Resources
Budget
Priority
Proj Mgmt
Estimates
Plan
Control
Communication
Requirements
Experience
Mgmt Advocacy
Process
Schedule
RISK OWNERS
raquo External and Business Risks PLM Directors Sales
raquo Organizational Risks Directors Managers
raquo Project Management Risks Project Managers Managers
raquo PBI Risks Product Owners Sprint Teams
raquo Tasks Risks Sprint Teams
PBIsTasks are Focus of Sprint Teams
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
RISK MANAGEMENT PROCESSTask Level for Sprint Planning
Perform Risk
Identification
Perform Risk
Analysis
Plan Risk
Response
Monitor and
Control RisksClose Risks
Review Risk
Areas
Identify
Potential Risks
Write Risk
Statements
Analyze List of
Risk
Statements
Identify Risks
to Track
Enter Risks in
TFS
Complete
Description amp
Data
Plan
Mitigation
Create tasks
ID Triggers
Plan
Contingencies
Execute
Mitigation
Tasks
Communicate
with Team
Track Changes
in TFS
Triggers
Expired
Tasks
Completed
Breakdowns
Resolved
Score
Probability amp
Impact
Breakdowns
Trigger
Contingencies
Record
Lessons
Learned
CATEGORIES OF RISKFocus of Task Risks Release
Project
Technical
Technology
Integration
Performance
Quality
External
Vendors
Regulations
Market
Customer
Org
Dependencies
Resources
Budget
Priority
Proj Mgmt
Estimates
Plan
Control
Communication
Requirements
Experience
Mgmt Advocacy
Process
Schedule
RISK OWNERS
raquo External and Business Risks PLM Directors Sales
raquo Organizational Risks Directors Managers
raquo Project Management Risks Project Managers Managers
raquo PBI Risks Product Owners Sprint Teams
raquo Tasks Risks Sprint Teams
PBIsTasks are Focus of Sprint Teams
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
CATEGORIES OF RISKFocus of Task Risks Release
Project
Technical
Technology
Integration
Performance
Quality
External
Vendors
Regulations
Market
Customer
Org
Dependencies
Resources
Budget
Priority
Proj Mgmt
Estimates
Plan
Control
Communication
Requirements
Experience
Mgmt Advocacy
Process
Schedule
RISK OWNERS
raquo External and Business Risks PLM Directors Sales
raquo Organizational Risks Directors Managers
raquo Project Management Risks Project Managers Managers
raquo PBI Risks Product Owners Sprint Teams
raquo Tasks Risks Sprint Teams
PBIsTasks are Focus of Sprint Teams
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
RISK OWNERS
raquo External and Business Risks PLM Directors Sales
raquo Organizational Risks Directors Managers
raquo Project Management Risks Project Managers Managers
raquo PBI Risks Product Owners Sprint Teams
raquo Tasks Risks Sprint Teams
PBIsTasks are Focus of Sprint Teams
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
CREATING A RISK ITEM
raquo From the Task create the
linked Risk item
raquo The Task will be Affected
by the Risk
TFS Risk WIT
1
2
3
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
CREATING A RISK ITEMTFS Risk WIT (Cont)
raquo Will be linked to the task if you
started it from the task links
menu
raquo Probability allows 1 ndash 100 For
simplicity use 25() for Low 50
for Med and 75 for High Wersquoll get
more precise over time
raquo Likewise Impact allows 1
through 10 but just use 10 for
High 5 for Medium and 1 for Low
raquo Stick with Dev Doc and SQA
lsquoRisk torsquo options
raquo Leave Severity on default Wersquore
not going to use it for now
These options are changing soon
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
UPCOMING WIT CHANGESTFS Risk WIT (Cont)
raquo Priority Remove Priority from the form
raquo Severity Remove Severity from the form
raquo Risk to Replace current dropdown menu options with Requirements
Performance Customer Release Test Dependency
raquo Probability Remove lsquo(1-100)rsquo from the tag change the field to be a
dropdown with options of High Medium and Low set default to
Medium
raquo Impact Replace all current dropdown options with of High Medium
and Low set default
to Medium
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
MITIGATION AND CONTINGENCY PLANS
raquo Wersquove identified risks Now what Mitigation Planning
bull Avoid the consequences of a risk by having a mitigation plan This plan should be added
to your current task (design dev etc) to ensure the risk doesnrsquot materialize
raquo It happened anyway Now what Declare a breakdown and perform the Contingency Plan
bull The mitigation plan wasnrsquot enough Now fall back on Plan B the Contingency Plan This
is the plan you enable AFTER the risk has become a real issue Your task is now in a
state of breakdown
raquo Example
bull Risk If my pants are too big they will fall down causing embarrassment and offense
bull Mitigation Plan I shall wear a belt to keep my pants up
bull Contingency Plan If they still fall down Irsquom going to need to wear suspenders
bull Trigger Event
bull Cost of contingency Estimated $20 - $40
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
MONITOR AND CONTROLRisk Breakdown Handling
Sprint Planning Task Execution Demo Retrospective
Risk ID Analysis Response Planning Risk Monitor and Control Risk Closing Lessons Learned
Major breakdowns impact
other teams components
or the release Team must
report up to PO Mgr PMMonitor for breakdowns
handle task breakdowns
within the Sprint Team
ID Analyze and Plan early
PBI
Task or
WR
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
UPDATING WITH EXCEL
raquo Use Excel to track update status and publish back to TFS ndash your preference
raquo Scrum Master can query all related risks and update en masse during status meetings
raquo Risks should have a lifecycle within the sprint They should be closed once the trigger passes
(usually a date or event) or the contingency corrects the breakdown
raquo Monitor all risks until closed Keep the overall risk assessment lsquogreenrsquo by improving the
average risk exposure Mitigating should lessen the probability and impact so updates should
improve the Risk Item status
Expectations for monitoring
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
RISK AREAS
raquo Extended Data Risk High-level Identification (Web view) Risk High-level
Identification (OneNote)
raquo IDM IDM Risk Area Identification (Web view) IDM Risk Area Identification
(OneNote)
THANK YOU
wwwitroncom
THANK YOU
wwwitroncom