BT

InfoQ Homepage Risk Management Content on InfoQ

  • Three Major Cybersecurity Pain Points to Address for Improved Threat Defense

    Three pain points every company must address when addressing cybersecurity include threat volume and complexity, a growing cybersecurity skills gap, and the need for threat prioritization. This article describes each of these in some detail, and includes recommendations for corporations to deal with them.

  • How Developers Can Learn the Language of Business Stakeholders

    This article explores how business stakeholders and developers can improve their collaboration and communication by learning each other's language and dictionaries. It explores areas where there can be the most tension: talking about impediments and blockers, individual and team learning, real options, and risk management.

  • Q&A on the Book Risk-First Software Development

    The book Risk-First Software Development by Rob Moffat views all of the activities on a software project through the lens of managing risk. It introduces a pattern language to classify different risks, provides suggestions for balancing risks, and explores how software methodologies view risks.

  • Sustainable Operations in Complex Systems with Production Excellence

    Successful long-term approaches to production ownership and DevOps require cultural change in the form of production excellence. Teams are more sustainable if they have well-defined measurements of reliability, the capability to debug new problems, a culture that fosters spreading knowledge, and a proactive approach to mitigating risk.

  • Cultivating a Learning Organisation

    This article explores how creating an internal culture of experimentation and learning enabled a company to keep pace with the rapid iterations in tech that have become the regular way we do business. It shows that psychological safety is a key component of the learning organisation; employees need to be able to experiment and learn from any outcome - without fear that failure will be punished.

  • Three Keys to a Successful “Pre-Mortem”

    Talking about what might go wrong acknowledges that many things are out of our control, and that we might mess up the things which are within our control. To have this conversation safely involves a structured activity called a pre-mortem. If held with some regularity, and always with creative problem solving time at the end, it can build a safe space for adaptation in the face of adversity.

  • What Should Software Engineers Know about GDPR?

    EU General Data Protection Regulation (GDPR) is moving out of the transition period next summer to become enforceable GDPR strongly emphasizes risk-based thinking; you take every step to mitigate privacy risks until the risks become something you can tolerate. As a software developer, this will affect you. This is what you need to know.

  • Q&A on The Antifragility Edge: Antifragility in Practice

    In the book The Antifragility Edge, Sinan Si Alhir shows how antifragility has been applied to help organizations evolve and thrive. He provides examples of how antifragility can be used beyond agility on an individual, collective (team and community) and enterprise level, and explores a roadmap for businesses to achieve greater antifragility.

  • Book Review: Site Reliability Engineering - How Google Runs Production Systems

    "Site Reliability Engineering - How Google Runs Production Systems" is an open window into Google's experience and expertise on running some of the largest IT systems in the world. The book describes the principles that underpin the Site Reliability Engineering discipline. It also details the key practices that allow Google to grow at breakneck speed without sacrificing performance or reliability.

  • Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!

    Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.

  • Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions

    This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.

  • Test Management Revisited

    The concept of test management sits awkwardly in agile, mostly because it’s a construct derived from the time when testing was a post-development phase, performed by independent testing teams. Agile, with its focus on cross functional teams, has sounded the death knell for many test managers. While test management is largely irrelevant in agile, there is still a desperate need for test leadership.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.