BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • DevOps @ Spotify

    This article is part of the “DevOps War Stories” series. Each month we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption. In this issue we learn how lessons learned from DevOps have permeated engineering management at Spotify. The result is a healthy Potlac with team leader, product owner, agile coach.

  • The Seven Information Smells of Domain Modelling

    Domain modelling is a powerful technique that many IT professionals have in their toolkit. Unfortunately a couple of issues with domain modelling have caused it to fall out of favour over the past few years, especially in Agile circles. Two real problems with the approach are that it takes too long, and that it is prone to “analysis paralysis”. This is an approach that addresses these issues.

  • Agile Software Architecture Sketches and NoUML

    Understanding the software architecture of what you're building can prevent chaos and encourage collective code ownership. In the race for agility though, many teams struggle to do this, particularly since they've abandoned UML in favour of "boxes and lines" sketches. Moving fast requires good communication, but how do you do this without resorting to big design up front and UML?

  • Interview with Michael Azoff from Ovum about How To Create the Agile Enterprise

    Large enterprises face three challenges: to innovate and act as a start-up, to use a budgeting process that keeps the organization’s strategy in touch with changing market conditions, and to transform the whole IT department to agile. Principal analyst Michael Azoff explains Ovum’s view on creating an agile enterprise.

  • The Real Question is Why?

    The Agile movement has driven a revolutionary change in the way we build and deliver software solutions. In the past few years Agile frameworks have become mainstream. Agile has solved the problems of the 90's and early 2000's. Now a new kind of problem is emerging that needs an equally elegant solution, how do we build the right solution? Do we know Why we are building it?

  • Bridging the Management Gap

    As Agile becomes widely accepted within IT organizations, one roadblock to more significant organizational change is becoming clear - resistance from management. Traditional command & control management no longer suffices in a globalized, knowledge-based economy. When will we reach the tipping point where organizations unshackle themselves from the limitations of command & control?

  • Kanban Pioneer: Interview with David J. Anderson

    David J. Anderson, pioneer in Kanban for software development, recently came to Brazil. A group of InfoQ Brasil editors interviewed David about Lean, Agile and Kanban. See the highlights of the interview.

  • Application Performance Management Maturity Model

    In this article, author Jim Hirschauer justifies the importance of application performance management (APM) process in organizations. He also describes a maturity model for application performance management with three different levels of maturity.

  • Evaluating Agile and Scrum with Other Software Methodologies

    Historical data is a key resource for judging the effectiveness of software process improvement methods and also for calibrating software estimation accuracy. In this article, Capers Jones compares Agile and Scrum with a sample of contemporary software development methods using several standard metrics.

  • Interview: Sam Haskins from Etsy on Code Deployment, Monitoring and Failure Procedures

    Sam Haskins from Etsy talks about code management with Github, fast deployments with feature flags and no packaging, canary releasing, voluntary code reviews, CI with Jenkins, monitoring and failures.

  • Queues – the true enemy of flow

    No-one wants IT projects to be late. But when they are, it’s rarely because of how long the actual work takes. Tasks and projects spend more time inactive, sitting in a queue, than being worked on. Despite this, most project management offices measure activity, not queues.This article examines why we should track queues and quantify their cost in order to make meaningful gains in speed of delivery

  • Interview and Book Excerpt: Mastering the Requirements Process

    Suzanne and James Robertson have released the 3rd edition of their book Mastering the Requirements Process. This edition includes material focused on the challenges of requirements in modern project environments, including agile and outsourcing relationships.

BT