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

  • Finding the Truth Behind Minimum Viable Products

    While the definition of Minimum Viable Product may work us into a tizzy, the goal behind it is extremely valuable for product companies: to rapidly learn what your customers want. Learning what your users want before you build it is good product development. Make sure when you do invest in a feature or solution, it’s the right one.

  • Article Series: Containers in the Real World - Stepping Off the Hype Curve

    This article series explains how containers are actually being used within the enterprise. It dives into the core technology behind containers and how this is currently being used by developers, examines core challenges with deploying containers in the enterprise and the future of containerisation, and discusses the role unikernels are currently playing within leading-edge organisations.

  • Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"

    Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.

  • Characteristics of a Great Scrum Team

    This article explores 'What makes a great Scrum team?' by offering detailed descriptions of the characteristics and skills needed in the Scrum roles of Product Owner, Scrum Master and Development Team.

  • Continuous Deployment with Containers

    Many of us have already experimented with Docker - for example, running one of the pre-built images from Docker Hub. However, a comprehensive build pipeline is required before deploying any containers into a production environment. This article outlines the steps you need to take for a fully automated continuous-deployment pipeline that builds microservices deployed via Docker containers.

  • Ten Ways to Successfully Fail your Agility

    This article is intended for newbies and agile sceptics who want to challenge their take on agile. It provides 10 ways to successfully fail your agility, implying that by replacing these practices with ones that do the opposite, you will increase agility and improve the odds of being successful.

  • State of the JavaScript Landscape: A Map for Newcomers

    Modern JavaScript development is in constant motion. Build tools that were popular 12 or even six months ago are no longer en vogue. In this article, Bonnie Eisenman gives JavaScript newcomers a map to get started on their JavaScript journey. For more experienced JavaScript developers, Bonnie provides an update on where the community is at and what technologies to use for new projects.

  • Q&A on the Scrum Field Guide - 2nd Edition

    The Scrum Field Guide - 2nd Edition by Mitch Lacey is a "what to expect" book for organizations transitioning to agile, which aims to help teams to deal with issues that occur and fine-tune their own implementation. An interview about the essentials of Scrum, sprint length, full time Scrum masters, making time available for solving defects, preventing bad hires, and increasing benefits from Scrum.

  • Build Your Own Offshore Development Team - or Not?

    When you absolutely positively MUST build your own offshore dev team to get the quality you need, consider NOT. There is an argument for ‘owning’ vs ‘renting’ when it comes to leveraging an offshore dev team, the author disagrees with the idea that building one’s own team is better than outsourcing the job. He knows what it takes to do it right, and it isn't easy.

  • Key Takeaway Points and Lessons Learned from QCon London 2016

    This article summarizes the key takeaways and highlights from QCon London 2016 as blogged and tweeted by QCon's 1,400 attendees. Over the course of the next 4 months, InfoQ will be publishing most of the conference sessions online, including 21 video interviews that were recorded by the InfoQ editorial team.

  • 0 Bugs Policy

    Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.

  • 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