BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Governance Content on InfoQ

  • Q&A on the Book "A Seat at the Table"

    In the book A Seat at the Table Mark Schwartz explains how the traditional role of the CIO conflicts with an agile approach for software development. He explores what IT leadership looks like in an agile environment, advising CIOs to set a vision for IT and take accountability for business outcomes.

  • Virtual Panel: Microservices Interaction and Governance Model - Orchestration v Choreography

    The recent trend in application architectures is to transition from monolithic applications to a microservices model. This transition without a good service interaction model will most likely result in chaos and a service landscape that's hard to govern and maintain. InfoQ spoke with domain experts on this topic and compiled their responses in this virtual panel article

  • Culture May Eat Agile for Breakfast

    Making culture your priority during the scaling phase of your organization is a sound business decision. You have to invest by hiring for mindset and educating everyone joining the organization in agile principles to prevent turning an existing agile culture into a traditional one.

  • Q&A with Immuta on the Implications of EU’s General Data Protection Regulation (GDPR)

    InfoQ talked with Immuta’s Andrew Burt and Steve Touw, to better understand the implications and challenges of the EU's Global Data Protection Regulation, which will come into effect in May 2018.

  • Version Control, Git, and your Enterprise

    This article is about understanding Git – both its benefits and limits – and deciding if it’s right for your enterprise. It is intended to highlight some of the key advantages and disadvantages typically experienced by enterprises and presents the key questions to be contemplated by your enterprise in determining whether Git is right for you and what you need to consider in moving to Git.

  • Updated Principles of Service Orientation

    Our understanding of SOA has changed over the last 15 years including new aspects such as Service Execution Context and a re-defined notion of the Service Contract. This paper reviews and updates the Principles of Service Orientation based on the first OASIS SOA RAF standard bridging the gap between business and technology and eliminating technology-specific wording in their formulation.

  • How SOA Governance (and SOA Management) Should Actually Be Done

    Ganesh Prasad proposes separating governance and management in large SOA projects to make sure that right dependencies are used throughout the system in order to promote agility, lower operating costs and reduced operational risks.

  • Q&A with Barry Boehm and Richard Turner on The Incremental Commitment Spiral Model

    The Incremental Commitment Spiral Model describes a process model generator. InfoQ interviewed the authors about the principles underlying the Incremental Commitment Spiral Model (ICSM), applying the ICSM, benefits that organization can get from it, and how organizations can use the ICSM to determine under what conditions to use software-intensive agile frameworks like Scrum, DSDM, SAFe, or DAD.

  • Virtual Panel: Convergence of SOA Governance and API Management

    There's recently been a lot of discussion about the convergence of SOA Governance and API Management. Services and APIs appear to deal with similar concerns, but historically the approach & philosophy has been different. Is there convergence and how? InfoQ spoke to a panel of SOA Governance and API Management experts to garner their views.

  • Converging API Governance and SOA Governance

    Achieving Service Oriented Architecture initiative success requires creating loosely coupled consumer-provider connections, enforcing a separation of concerns between consumer and provider, exposing a set of re-usable, shared services, and gaining service consumer adoption. Many development teams publish SOA services, yet struggle to create a service architecture that is widely adopted.

  • 3 years of Kanban at Sandvik IT: Sustaining Kanban in the Enterprise

    This second article in the “3 years of Kanban at Sandvik IT” series focuses on the lessons that the System Development Office learned when sustaining the Kanban method during this 4 years journey. Presented are four qualities that Sandvik IT identified as key when setting-up relevant, and long-term, kanban systems in the enterprise: Stickiness, Clarity, Curiosity and Influence.

  • Author Q&A – The Lean Mindset by Tom and Mary Poppendieck

    The Lean Mindset is a collection of research results and case studies from companies applying lean in product development and delivery. A lean mindset according to Mary and Tom Poppendieck is about “developing the expertise to ask the right questions, solve the right problems, and do the right thing in the situation at hand”.

BT