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

  • New Book on Docker Provides Comprehensive Introduction

    Docker in Action, written by Jeff Nickoloff, provides a comprehensive introduction to Docker and how to integrate it into a development workflow. This book is intended for developers and operations engineers who wish to adopt Docker for application development and integrate it into their software delivery process.

  • Researcher Recognized for Advances in Team Performance Techniques

    Eduardo Salas is recognized by the APA for his 30 years of research on team work. His implementation of team training includes defining team structure, identifying specific communication needs, clarifying roles and leadership skills, and practicing with scenarios. This technique has been used across many fields of work, and is part of the program as NASA prepares to send a team to Mars.

  • Agile Executive Forum 2016 Summary

    The Agile Alliance hosted a one-day Executive Forum in San Jose, CA on September 19. The event attracted participants from around the world and a range of senior speakers from large organisations, and focused on how adopting agile development impacts companies and what executives need to do to help ensure successful cultural transformation, which is what agile adoption at scale is about.

  • Scaling Scrum to Build a New-Technology Printer

    When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.

  • Refactoring and Code Smells – A Journey Toward Cleaner Code

    Refactoring helps to move towards cleaner code that is easier to understand and maintain. It takes practice and experience to recognise code smells: symptoms of bad design which indicate deeper problems in the code. Tools can be helpful to refactor in small steps and prevent breaking the code.

  • Rethink Leadership: Being Ordinary to Accomplish Extraordinary Results

    Ordinariness in leadership can help us to accomplish extraordinary results, argues agile/lean coach Katherine Kirk. Several more people have explored approaches that suggest to rethink leadership and go back to behaviour basics for leading people. Although these approaches are about small ordinary things, their effect may cause a revolution in the way organizations are being managed.

  • Refuting the Idea of Rewriting the Agile Manifesto

    Alistair Cockburn recently posted his viewpoint on the history of the Agile Manifesto, from the perspective of one of the original authors and signatories. He encourages readers to understand the perspective taken at the time by the authors, and also to explore the ongoing work of many of the original signatories. The original authors explicitly refuted the idea of rewriting the manifesto.

  • How Agile and Architecture Parted and Finally Became Friends

    People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.

  • Agile 2016: Lee Cunningham on Scaling Agile and VersionOne

    At the recent Agile 2016 conference Lee Cunningham, VersionOne’s Senior Director of Enterprise Agile Strategy, spoke to InfoQ about scaling agile, expanding agile beyond IT, identifying value and the direction of the VersionOne platform.

  • Key Takeaways from the 'Agile on the Beach' 2016 Conference: Day One

    At the sixth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key takeaways included the value of the scientific method to drive change; the use of Continuous Delivery (CD) for improving safety and speed; and the power of cognitive bias during the user testing.

  • Benefits of Agile Transformation at Barclays

    Increased throughput, reduced code complexity, less production incidents, shorter deployment cycles and higher happiness in teams; these are some of the benefits that the agile transformation at Barclays has delivered. Within the first year of the transformation, which is based on Disciplined Agile, more than 800 teams adopted agile making this one of the largest agile implementations.

  • Box Open-Sources Continuous Localization Platform Mojito

    Box has open-sourced their continuous localization platform, Mojito. The product consists of a CLI that collects and integrates strings for translation and a web app that provides an interface for translators to keep track of their work.

  • Agile in Dispersed or Distributed Teams

    Cross-cultural team building enables collaboration and teamwork in dispersed or distributed agile teams. You need to invest to get the best out of a dispersed team. An exploration about what is needed to make agile work with dispersed or distributed teams.

  • Getting the Data Needed for Data Science

    Data science is about the data that you need; deciding which data to collect, create, or keep is fundamental argues Lukas Vermeer, an experienced Data Science professional and Product Owner for Experimentation at Booking.com. True innovation starts with asking big questions, then it becomes apparent which data is needed to find the answers you seek.

  • Continuous Deployment at Coolblue

    Continuous deployment results in a higher sense of responsibility and better quality of deployments, argues Paul de Raaij, technical pathfinder at Coolblue. Coding standards prevent your code base from becoming a mess, automated inspections are great for tedious and boring checks, and manual checks are great for checking if the logic or use of code actually makes sense.

BT