BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Collaboration Content on InfoQ

  • Interview with Simon Baker, Author of No Bull

    InfoQ has interviewed Simon Baker, cofounder of Energized Work and the 2009 recipient of the Agile Alliance Gordon Pask Award, author of the "No bull" publication on the past 12 years of Agile.

  • Agile Adoption – Vital Behaviours and Influence Strategies

    Steve is interested in uncovering better ways to deliver successful projects regardless of whether or not those ways are ‘agile’. After reading "Influencer, the Power to Change Anything" he found a set of behaviours and influence strategies that are helpful for giving projects the best chance for success and also for helping teams transition to agile.

  • Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

    In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.

  • Laurent Bossavit: Agile Ten Years On

    Laurent Bossavit discusses the importance of learning from history and reflects on the historical influences that have contributed to emergence of agile practices and techniques. He examines the impact agile approaches are having and the emergence of the new discipline of agile software development, and calls for formulation of a new generation of more inclusive Agile institutions.

  • New book - Individuals and Interactions: An Agile Guide

    Ken Howard and Barry Rogers have written a book that focuses on the first value from the Agile Manifesto. They provide advice, tools and techniques to help teams and individuals improve their communications and interpersonal interactions. The book presents a set of tools that work together more effectively. They provide guidelines for a workshop to put the techniques into practice.

  • Git, Gerrit Review and Jenkins or Hudson CI Servers

    Together, Gerrit and Jenkins/Hudson allow you to propose changes and have those proposals automatically compiled/tested/verified before a human review even starts. This article shows how to install and configure Gerrit and how to hook it up to Jenkins/Hudson to build all proposed changes.

  • Interview: William E. Perry - Author iTeams – Putting the “I” Back Into Team

    In his book, iTeams – Putting the “I” Back Into Team, author William E. Perry demolishes the cliché - "There is no ‘I’ in team." As Perry explains, the phrase is nonsense because it is the individual differences in team members that make teams great. In this interview, Ben Linders explores with the author the motivations for writing the book as well as some of the key thoughts.

  • Agile Architecture Interactions

    James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility.

  • The Art of Creating Whole Teams: how agile has changed the way we work with our customers

    Angela Martin earned her PhD examining how agile methods work in practice and what is different about this way of working. She shares some of the key practices which organisations can implement to increase their likelihood of successful cultural change through creating Whole Teams - truly cross functional collaborative teams working well together to deliver products which meet customer's needs

  • Breaking Down Walls, Building Bridges, and Takin’ Out the Trash

    Agile Team Rooms can help double the productivity of an Agile Team. Most people are familiar with the Caves and Commons approach where the team has a common area on the inside of the room and private desks on the outside. Some teams dispense with the private spaces in the room, but few go as far as Menlo dispensing with the rooms altogether.

  • Use of Kanban in the Operations Team at Spotify

    In this article, InfoQ spoke with Mattias Jansson, Operations Engineer at Spotify (an online music streaming service) about the adoption of Kanban by the Spotify Operations team. Jansson offered a lot of detail about the choice to adopt Kanban as well as the experiences that the Operations team at Spotify has gained while implementing a Kanban-based approach to dealing with their workload.

  • Working with the Product Backlog

    Roman Pichler discusses the product backlog along with techniques for effectively grooming it. Complicated applications of the product backlog are covered as well as how to handle nonfunctional requirements and how to scale a product backlog for large projects. This is a chapter excerpt from Roman's book: Agile Product Management with Scrum.

BT