Risks are defined here as anything that can affect delivery of critical stakeholder values, including quality requirements, or which can negatively affect resource consumption in the short term or long term.Risk management needs to permeate all aspects of IT projects and operations.
Risks are everybody’s responsibility, at a very detailed level of planning requirements, contracts, architecture and implementation.
Our free practical tools can be used on a daily basis when planning and discussing IT projects by all levels of experts, managers, business analysts, architects and system or software engineers.
--------------------------------------------------------------------------------
Speaker: Tom Gilb Hon FBCS
---------------------------------------------------------------------------------
AGENDA
08:45 - 09.00 – Refreshments and networking.
09:00 - 17:00 - Course with approx finish time.
--------------------------------------------------------------------------------
SYNOPSIS
Our risk management methods consist of a large number of free practical tools, which can be added to your current methods incrementally.
Our risk management methods represent a new fresh view of the risk area. The methods are proven in practice. They are adopted and practiced by leading Corporations worldwide, but still not pervasively known to most professionals or taught on most risk courses.
They are Advanced Risk Management opportunities.
Basic Risk Management
1.1 Risk Related Concepts:
- Threats, Attacks, Mitigation, Built in Mitigation, Damage
- Slip, Error, Mistake, Bug, Defect, Major Defect, Defect Density, Defect Cost
1.2 Basic Risk Management Methods.
- The weaknesses with conventional risk management methods.
- Capturing risks during planning: requirements, architecture, strategy, contracting, installation planning, test planning. The Planning Language approach.
- Project Risk Management : identifying risks during project building and incremental delivery.
- Dynamic Design to Costs (Quinnan, IBM FSD Cleanroom)
- Risk Management using Specification Quality Control
- Risk Management using Defect prevention Process (Lean continuous process improvement method, ‘DPP’)
1.3 Requirements Risk Management.
- Quality and value Requirements risk management
- Relationships risk management
- Conflicting requirements risk management
1.4 Design and Architecture Risk Management
- Design risk management by decomposition to smaller value deliveries
- Design risk management by estimation of multiple values, qualities and costs
- Design risk management by Dynamic Design to Cost (advanced agile)
1.5 Cost Estimation Risk Management.
- The basic problems with conventional cost estimation: why it is doomed to fail
- How to do design to cost
- How to prioritize value for money so risks don’t hit so hard
- Dynamic Design to cost delivers on time under budget (Cleanroom and Evo experiences)
1.6 Contacting Risk Management.
- Who should bear the risk of deviation?
- The flexible contracts templates: Agile Contracting
--------------------------------------------------------------------------------
SPEAKER BIOGRAPHIES
Tom Gilb joined IBM in 1958. He has been an international consultant and teacher for 55 years. Written 10 published books. Competitive Engineering (2005), and Value Planning (2016). Tom has developed advanced methods for developing systems of any kind, with emphasis on IT systems and High Quality systems.
He is Honorary Fellow of BCS.
Tom Gilb and his partner Kai Gilb have, together with many professional friends and clients, personally developed the Agile ‘Engineering’ methods they teach. The methods have been developed over five decades of practice all over the world in both small companies and projects, as well as in the largest companies and projects. Their website www.Gilb.com/ offers free papers, slides, books, videos, and cases about Agile and many other subjects.
There are many organisations, and individuals, who use some or all of their methods. IBM and HP were two early corporate-wide adopters (1980, 1988). Recently (2016) over 20,000 engineers at Intel have voluntarily adopted the Planguage requirements specification methods; in addition to practicing to a lesser extent Evo, Spec QC and other Gilb methods.
Many other multinationals are in various phases of adopting and practicing the Gilb methods. Many smaller companies also use the methods.
Tom’s methods are 100% risk conscious and devoted to reducing the risks of failure and partial failure, by attention to the details and to the big picture.
--------------------------------------------------------------------------------
Please ensure that you bring a laptop or tablet to be able to access the presentation and associated documents.
THIS EVENT IS BROUGHT TO YOU BY: BCS Quality SG. To find out more, click here: https://www.bcs.org/category/10130
For overseas delegates who wish to attend the event please note that BCS does not issue invitation letters.
