On how the current top-down (command-and-)control approach, and the \'middle-out\' modelling aproach, will and can not work in the end. A new paradigm, bottom-up KISS risk management will be needed.
The document discusses how to implement risk-based testing in an agile environment. It outlines challenges faced when risk analysis is not properly integrated, such as risks not being translated to the product backlog or risk analysis not being updated each iteration. It then provides an overview of how to conduct risk-based testing by gathering requirements and risks, mapping them, calculating risk items, and developing strategies like using risk classes to determine test effort and prioritizing requirements in sprints based on risk analysis. This allows coverage of both requirements and risks to be tracked.
In a reliability evaluation test, one could end up with one of decisions of the reliability specification being met, not met, or inconclusive. In this presentation, we present a methodology of sample size determination prior to the test based on the probability of reaching these decisions. The specific results are obtained for the cases of Exponential distribution and Weibull distribution with a known shape parameter.
Jonathon Simon, a senior manager at Ernst & Young, presented on risk management. He discussed (1) defining risk management and the risk management lifecycle, (2) examples of good and bad risk management practices, and (3) critical success factors for effective risk management including being proactive and conducting regular risk assessments and scenario planning. The presentation also included an EY case study about implementing robust risk management processes for a government health project.
This document discusses various approaches to analyzing system failures and outages, including root cause analysis. It notes that sequence-of-events analysis can oversimplify issues and ignore surrounding context. Epidemiological models that view failures as resulting from the alignment of multiple factors are preferable. Truly understanding failures requires examining how organizational, technical, and human factors interact as a complex system over time.
Nagios Conference 2012 - Kishore Jalleda - Nagios in the Agile DevOps Continu...Nagios
?
Kishore Jalleda's presentation on using Nagios in a continuous development environment.
The presentation was given during the Nagios World Conference North America held Sept 25-28th, 2012 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/nwcna
\'Cloud\' brings many advantages. Among others, that much of your social media data will disappear ever more quickly -- as all the storage in the world cannot keep up with the growth of Big Data, hence ever more will be lost. For companies, that may be a problem...
The document discusses operational risk management. It summarizes that traditionally, information security has been approached from the bottom-up rather than top-down. It then critiques common risk management methodologies for making unrealistic assumptions and using oversimplified models that do not accurately capture complex relationships. The presentation goes on to argue that attempting to perfect bureaucracy and control through risk management leads to an illusion of being in control and a totalitarian system, as unforeseen events will always occur.
C:\Fakepath\Activity Project Management Atlas 2000Henk, van Soest
?
Activity is a growing organization that has developed extensive knowledge and experience in project management over the years, which it has documented in its ATLAS framework. The ATLAS provides a common framework for project management processes and terminology within Activity. It also serves as a methodology that can be tailored for clients who do not have their own project management approach. The ATLAS is intended to be practical and continually developed based on lessons learned from projects.
Improving UX through Application Lifecycle Managementgoodfriday
?
Learn how you can leverage Microsoft Expression and Microsoft Visual Studio Team System to improve your overall application lifecycle, decrease your time to market, and ultimately raise the quality of your applications.
The document discusses project management concepts and processes. It defines key terms like project, program, operations, and project management. It outlines the major knowledge areas of project management including integration, scope, time, cost, quality, human resources, communications, risk, and procurement. It also describes the five project management process groups of initiation, planning, execution, monitoring and control, and closing. Finally, it provides an example of dividing a typical project into defining, planning, implementation, and closing phases.
The document summarizes a team project to develop a website that connects Australian businesses and consumers. It outlines the team members and their personalities. It then discusses the current situation of distributed overseas services and poor website design/security for Australian businesses. The proposed solution is a searchable website to help businesses create affordable websites. Potential outcomes include boosting business, increased internet usage, and connecting isolated businesses. Metrics for success and risks/mitigations are also presented.
This document provides an introduction to Six Sigma. It discusses why quality initiatives are important, defines Six Sigma and its goal of reducing defects per million opportunities. It explains that Six Sigma provides a focus on critical to quality metrics and uses data and statistical processes to systematically solve problems. Key terms are introduced, such as processes, inputs, outputs, the relationship between reducing variation and reducing defects. The roles of different Six Sigma team members are also outlined.
Tech Ed 2009 Practical Tips To Manage Projects Productivelyrsnarayanan
?
The document discusses tips for productive project management. It outlines goals of productive project management such as delivering on time, cost and quality. It discusses the role of a project manager and focusing on planning through tools like work breakdown structure and defining, delegating, and ensuring tasks are completed. The document provides examples and emphasizes raising early flags, stating assumptions, assessing competence, and educating clients to improve productivity.
The document discusses using probabilistic risk analysis and Monte Carlo simulation to increase the probability of project success. It explains that modeling tasks as probability distributions rather than single point estimates allows for a more accurate assessment of overall schedule and budget risk. Capturing the uncertainty and dependencies between different tasks and cost/schedule drivers is important for generating reliable forecasts. The goal is to quantify confidence levels and establish appropriate margins to account for risks and uncertainties.
Workshop project risk management (29 june 2012)bfriday
?
The document discusses project risk management tools used by Bronwyn Friday, the Group Manager of Risk at John Holland Group. It provides an overview of Bronwyn's background and experience in risk management. It then discusses tools and best practices for project risk management, including qualitative and quantitative risk assessment tools, risk registers, and risk identification methods like brainstorming workshops.
This document outlines the agenda for a presentation on risk-informed decision making (RIDM). The presentation will cover:
1. The inherent riskiness of current uncertain times and the need to evolve risk management approaches to remain relevant.
2. An explanation of what RIDM is and why it is important now, given that continuous risk management (CRM) is already practiced.
3. Examples of when and why to use RIDM in addition to discussing the actual steps involved in conducting RIDM.
The presentation aims to demonstrate how RIDM can help risk management practices evolve to address a more dynamic environment with changing mission objectives and resources. RIDM is presented as a complement to
Five risk management rules for the project managerJohn Goodpasture
?
The document outlines five rules for risk management:
1) There are no objective estimates of the future due to cognitive biases like anchoring and availability. Facts are in the past while estimates rely on perception.
2) Requirements are never fully complete since it's impossible to imagine everything.
3) Central tendency smoothing washes out asymmetrical extremes, with pessimism and optimism balancing out.
4) Confidence in schedules degrades exponentially after work streams merge due to merge bias.
5) Probabilistic risk analysis models like FMEA are needed for systems with many interdependent parts, to understand behavior and failures.
This document provides an overview of Six Sigma Yellow Belt training objectives and concepts. The objectives are to understand the need for Six Sigma and explain the DMAIC process. Key Six Sigma concepts covered include: the history and focus on reducing defects, standard deviation and the sigma scale, the DMAIC methodology of Define, Measure, Analyze, Improve, and Control problems, and how Six Sigma can be applied to any business function. An example of applying Six Sigma to improve a pizza delivery service is also provided.
This document outlines a model for creative problem solving and decision making. It discusses moving from simple to complicated to complex problems. The model includes stages like define, discover, develop, decide and deliver. It presents tools that can be used at each stage and level of problem complexity. These include techniques like brainstorming, 5 whys, assumption busting and more. The document provides an overview of a problem solving model and principles and suggests training modules to help with implementation.
The document discusses developing a business case for requesting project funding. It provides context on the need for IT project planning given executive scrutiny of IT investments. Poor methodology currently wastes time on good ideas that do not get funded. The solution presented is to utilize Project Management Body of Knowledge (PMBOK) principles to create a more credible business case that improves the chance of funding. The benefits are outlined as improving the opportunity for capital budget requests to be approved.
Presented at the 2012 Construction CPM Conference, this presentation walks through the challenges of owner/contractor and JV disputes and reviews solutions and prevention techniques using Fuse.
This document outlines the purpose and importance of implementing basic project management techniques for ATW projects at CREC. The key points are:
1) Implementing project management will increase understanding of the techniques, help manage ATW projects more effectively, increase credibility, and reduce stress.
2) Projects currently have a low success rate of 30-35%, and CREC's future depends on successful execution of ATW projects.
3) Project management provides a framework to help define projects, plan tasks and resources, execute plans, control costs and schedules, and close out projects. This can help improve the success rate of ATW projects.
This document provides information about Ambe Engineering, including their expertise in cost, operational and management improvement initiatives primarily for the automotive and heavy truck industries. It details their staff experience and locations. It then outlines their mission to improve profitability through problem solving, resource support, cost reduction, quality improvement, and other initiatives. Several case studies and areas of expertise are described related to warranty analysis, competitive cost analysis, and their problem solving methodology.
IDC Amsterdam 2013 09 12 Smart Security Solutions require Ditto DesignsJurgen van der Vlugt
?
How we exclude people from information security (design) which takes away the overwhelmingly biggest threat-AND-vulnerability; how we need to ditch the top-down compliance approach, and how to do security bottom-up. KISS.
The document discusses operational risk management. It summarizes that traditionally, information security has been approached from the bottom-up rather than top-down. It then critiques common risk management methodologies for making unrealistic assumptions and using oversimplified models that do not accurately capture complex relationships. The presentation goes on to argue that attempting to perfect bureaucracy and control through risk management leads to an illusion of being in control and a totalitarian system, as unforeseen events will always occur.
C:\Fakepath\Activity Project Management Atlas 2000Henk, van Soest
?
Activity is a growing organization that has developed extensive knowledge and experience in project management over the years, which it has documented in its ATLAS framework. The ATLAS provides a common framework for project management processes and terminology within Activity. It also serves as a methodology that can be tailored for clients who do not have their own project management approach. The ATLAS is intended to be practical and continually developed based on lessons learned from projects.
Improving UX through Application Lifecycle Managementgoodfriday
?
Learn how you can leverage Microsoft Expression and Microsoft Visual Studio Team System to improve your overall application lifecycle, decrease your time to market, and ultimately raise the quality of your applications.
The document discusses project management concepts and processes. It defines key terms like project, program, operations, and project management. It outlines the major knowledge areas of project management including integration, scope, time, cost, quality, human resources, communications, risk, and procurement. It also describes the five project management process groups of initiation, planning, execution, monitoring and control, and closing. Finally, it provides an example of dividing a typical project into defining, planning, implementation, and closing phases.
The document summarizes a team project to develop a website that connects Australian businesses and consumers. It outlines the team members and their personalities. It then discusses the current situation of distributed overseas services and poor website design/security for Australian businesses. The proposed solution is a searchable website to help businesses create affordable websites. Potential outcomes include boosting business, increased internet usage, and connecting isolated businesses. Metrics for success and risks/mitigations are also presented.
This document provides an introduction to Six Sigma. It discusses why quality initiatives are important, defines Six Sigma and its goal of reducing defects per million opportunities. It explains that Six Sigma provides a focus on critical to quality metrics and uses data and statistical processes to systematically solve problems. Key terms are introduced, such as processes, inputs, outputs, the relationship between reducing variation and reducing defects. The roles of different Six Sigma team members are also outlined.
Tech Ed 2009 Practical Tips To Manage Projects Productivelyrsnarayanan
?
The document discusses tips for productive project management. It outlines goals of productive project management such as delivering on time, cost and quality. It discusses the role of a project manager and focusing on planning through tools like work breakdown structure and defining, delegating, and ensuring tasks are completed. The document provides examples and emphasizes raising early flags, stating assumptions, assessing competence, and educating clients to improve productivity.
The document discusses using probabilistic risk analysis and Monte Carlo simulation to increase the probability of project success. It explains that modeling tasks as probability distributions rather than single point estimates allows for a more accurate assessment of overall schedule and budget risk. Capturing the uncertainty and dependencies between different tasks and cost/schedule drivers is important for generating reliable forecasts. The goal is to quantify confidence levels and establish appropriate margins to account for risks and uncertainties.
Workshop project risk management (29 june 2012)bfriday
?
The document discusses project risk management tools used by Bronwyn Friday, the Group Manager of Risk at John Holland Group. It provides an overview of Bronwyn's background and experience in risk management. It then discusses tools and best practices for project risk management, including qualitative and quantitative risk assessment tools, risk registers, and risk identification methods like brainstorming workshops.
This document outlines the agenda for a presentation on risk-informed decision making (RIDM). The presentation will cover:
1. The inherent riskiness of current uncertain times and the need to evolve risk management approaches to remain relevant.
2. An explanation of what RIDM is and why it is important now, given that continuous risk management (CRM) is already practiced.
3. Examples of when and why to use RIDM in addition to discussing the actual steps involved in conducting RIDM.
The presentation aims to demonstrate how RIDM can help risk management practices evolve to address a more dynamic environment with changing mission objectives and resources. RIDM is presented as a complement to
Five risk management rules for the project managerJohn Goodpasture
?
The document outlines five rules for risk management:
1) There are no objective estimates of the future due to cognitive biases like anchoring and availability. Facts are in the past while estimates rely on perception.
2) Requirements are never fully complete since it's impossible to imagine everything.
3) Central tendency smoothing washes out asymmetrical extremes, with pessimism and optimism balancing out.
4) Confidence in schedules degrades exponentially after work streams merge due to merge bias.
5) Probabilistic risk analysis models like FMEA are needed for systems with many interdependent parts, to understand behavior and failures.
This document provides an overview of Six Sigma Yellow Belt training objectives and concepts. The objectives are to understand the need for Six Sigma and explain the DMAIC process. Key Six Sigma concepts covered include: the history and focus on reducing defects, standard deviation and the sigma scale, the DMAIC methodology of Define, Measure, Analyze, Improve, and Control problems, and how Six Sigma can be applied to any business function. An example of applying Six Sigma to improve a pizza delivery service is also provided.
This document outlines a model for creative problem solving and decision making. It discusses moving from simple to complicated to complex problems. The model includes stages like define, discover, develop, decide and deliver. It presents tools that can be used at each stage and level of problem complexity. These include techniques like brainstorming, 5 whys, assumption busting and more. The document provides an overview of a problem solving model and principles and suggests training modules to help with implementation.
The document discusses developing a business case for requesting project funding. It provides context on the need for IT project planning given executive scrutiny of IT investments. Poor methodology currently wastes time on good ideas that do not get funded. The solution presented is to utilize Project Management Body of Knowledge (PMBOK) principles to create a more credible business case that improves the chance of funding. The benefits are outlined as improving the opportunity for capital budget requests to be approved.
Presented at the 2012 Construction CPM Conference, this presentation walks through the challenges of owner/contractor and JV disputes and reviews solutions and prevention techniques using Fuse.
This document outlines the purpose and importance of implementing basic project management techniques for ATW projects at CREC. The key points are:
1) Implementing project management will increase understanding of the techniques, help manage ATW projects more effectively, increase credibility, and reduce stress.
2) Projects currently have a low success rate of 30-35%, and CREC's future depends on successful execution of ATW projects.
3) Project management provides a framework to help define projects, plan tasks and resources, execute plans, control costs and schedules, and close out projects. This can help improve the success rate of ATW projects.
This document provides information about Ambe Engineering, including their expertise in cost, operational and management improvement initiatives primarily for the automotive and heavy truck industries. It details their staff experience and locations. It then outlines their mission to improve profitability through problem solving, resource support, cost reduction, quality improvement, and other initiatives. Several case studies and areas of expertise are described related to warranty analysis, competitive cost analysis, and their problem solving methodology.
IDC Amsterdam 2013 09 12 Smart Security Solutions require Ditto DesignsJurgen van der Vlugt
?
How we exclude people from information security (design) which takes away the overwhelmingly biggest threat-AND-vulnerability; how we need to ditch the top-down compliance approach, and how to do security bottom-up. KISS.
On the necessary re-design of security controls. To provide guiding rails to keep only those that sway too far out, instead of slamming everyone into compliance with too-tight rails.
1) The document discusses the future of risk management and outlines some issues with current approaches.
2) Regulations like Basel II aimed to improve risk management but ended up creating large compliance overhead without meaningfully addressing operational risks.
3) Guidance can go wrong when it is poorly understood, implemented as directives rather than suggestions, and lacks clarity around definitions, classifications and how to apply results. This led to formal compliance without better risk management.
NGI Regio Rdam / Afd IT-A: Stuxnet - Beveiliging en Audit van Proces ITJurgen van der Vlugt
?
Het verhaal over hoe Stuxnet een wake-up call is voor IT-auditors, of dat zou moeten zijn. En wat \'wij\' informatiebeveiligers / IT-auditors kunnen leren van de proces-IT-wereld, en andersom. Er is nog veel te doen...
The document discusses the Stuxnet worm and issues with process control systems (SCADA/ICS). It notes that Stuxnet targeted Siemens WinCC/PCS7 systems used in industrial control and exploited previously unknown vulnerabilities. The talk will cover process control systems, their components and architecture, problems with current security approaches, potential consequences of failures or attacks, and the need for improved controls and a control loop approach to security management.
8. De Toekomst¡
? ALLE risicodiscussie is subjectief
? Gaat over de toekomst,
? De ? van onzekerheid
? Bestaat alleen in de verbeelding
? RM is speculeren over de toekomst
? Toch¡ amechtige pogingen
9. Overhead
Evaluate design & Analysis Monitor & react
set-up
Operational Risk Problem
Management Mgt
Incidents
ORAP Inherent for analysis
Controls Risk indicators
risks (Problems)
R(S)A (K)ORC KRI Incident
(+Audit) (Mgt) (Mgt) Mgt Insu-
Near rance
Designed, Tuning,
Selected for Mandatory
misses CLD Mgt
efficiency
Corrective
KRI actions
values Incidents Indemnities
Process
Breach
Very, very basically
Surprise!
14. Initi?le auditissues Forecast ultimo 2011
1 2
3 4 4 3
5
9
7 8 6
9
Kans
Kans
6
2
7
1
Impact Impact
? 1 Kans Kansloos
? ¡ per? jaar? transactie? nanoseconde?
? 1 Impact Kansloos
? ¡ Alleen financieel? reputatie, etc.? tijd; vs ingrijpen?
? H x H = 25 Kansloos
? 3xM=H Kansloos
? ¡¯16¡¯ > ¡¯12¡¯ Kansloos
? Wie schat ¡®H¡¯; hoe en met welk ¡®bewijs¡¯?
15. In particular, for any consistent,
effectively generated formal theory that
proves certain basic arithmetic truths,
there is an arithmetical statement that is
true, but not provable in the theory.
Kurt G?del
No matter how perfect you try to risk
manage, incidents will happen
Yours Truly
16. ¡Ò ( Kansfunctie ¡Á? Impactfunctie )
¡Æ( Kosten van tegenmaatregelen )
Voor vele series van functies en parameters, impact
schattingsranges (¡), variabele sets van tegenmaatregelen
Inclusief variabele maten van effectiviteit, met vage noties van
risk appetites in de achterhoofden van sommigen
21. En dan zijn er nog kosten
What was it astronaut John Glenn said
went through his mind as he awaited
lift-off?
"You're thinking you're sitting on top of
the most complex machine ever built
by man, with a million separate
components, all supplied by the lowest
bidder."
22. Ja Maar ¡
1. Yes we know all that. Nothing¡¯s perfect.
2. The assumptions are reasonable.
3. The assumptions don¡¯t really matter.
4. The assumptions are conservative.
5. You cannot prove the assumptions are wrong.
6. We only do what everyone else does.
7. The decision maker is better off with us than without us.
8. The models are not completely useless.
9. You gotta make the best of the data you¡¯ve got.
10. You need assumptions to make progress.
11. The models deserve the benefit of the doubt.
12. Models and assumptions don¡¯t do any harm so why bother ¡?
? David Freedman (in Nassim Taleb¡¯s Black Swan)
23. Combinaties
Externe data Scenario?s
? Relevantie; toepasselijkheid
(modereren vs bias)
? Resultaten uit het verleden
? Te weinig data (?)
? Self-reporting !?
? Veel (!) te weinig data; kwaliteit ? Te weinig data (?)
? Self-reporting !? ? Kennis, zicht op risico¡¯s
? Resultaten uit het verleden ? Zuiver en alleen lokaal bruikbaar
? Kennis en kunde
Interne data ? Percepties van risico RSA?s
28. Bottom-up dan ..?
In theory, nothing works, In practice, everything works,
and everyone knows why. but no-one knows why.
We have in our organisation a combination
of theory and practice.
35. J. R. Galbraith, "Organization Design: An Information Processing View" Interfaces, 4 (1974), 28-36 Summary
Galbraith believes that "the greater the uncertainty of the task, the greater the amount of information that must be
processed between decision makers during the execution of the task to get a given level of performance". Firms
can reduce uncertainty through better planning and coordination, often by rules, hierarchy, or goals.
Galbraith states that "the critical limiting factor of an organizational form is the ability to handle the non-routine
events that cannot be anticipated or planned for".
When the "exceptions" become too prevalent, they overwhelm the hierarchy's ability to process them. Variations in
organization design arise from different strategies to increase planning ability and to reduce the number of exceptional
events that management must resolve.
Galbraith defines a continuity of organizational forms that firms utilize to reduce uncertainty:
1. Creation of Slack Resources. These include extending delivery times, adding more money to the budget, and
building inventory (all which have inherent costs). If a firm fails to actively create a higher level strategy to address
uncertainty, this strategy will occur by default.
2. Creation of Self-Contained Tasks. One strategy at this level is changing from functional to product groups.
3. Investment in Vertical Integration Systems. Condensing the flow of information by building specialized languages
and computer systems can help analysis and decision making.
4. Creation of Lateral Relationships. Moving the decision making power down in the firm to where the information
exists can reduce uncertainty at the decision level.
There are various strategies of increasing complexity to achieve this:
A. Direct contact between managers across groups
B. Liaison personnel between groups.
C. Task Forces
D. Teams
E. Cross-group Managers (project managers, program managers, etc.)
F. Linked Managers (with power over some cross-group resources)
G. Matrix Organization
38. Conclusie
? Risk Management op de huidige manier,
werkt niet
? Gedreven door CYA, angst voor de wereld
? RM of the Universe is een fantasie
? Idealen bijstellen,
via Bottom-up (andere) idealen halen