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

  • Collaborative Software Development Platforms for Crowdsourcing

    In this IEEE article, authors provide an overview of current technologies for crowdsourcing in software development. They talk about the requirements, current practice and trends in collaborative platforms.

  • Why Do We Need Self-Organising Teams?

    Change is the only constant in our world and “business agility” is demanded. Our old maps for running organisations are no longer valid; we need new ones based on systemic thinking. This second article from a series on Leading Self-Organising Teams discusses why we need self-organising teams.

  • Exploring the ENTIRE DevOps Toolchain for (Cloud) Teams

    When assessing technology that empowers a DevOps transformation, it’s easy to focus in on the headline capabilities (“configuration management!”) and miss out on the bigger picture. How can teams shipping cloud (or on-premises) applications use the full suite of DevOps technologies to simplify delivery and management at scale? This article classifies and explains key enabling technologies.

  • 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”.

  • Solving the Gordian Knot of Chronic Overcommittment in Development Organizations

    Why do we promise more than we can deliver? Why do we say yes when we are already too busy? Chronic Overcommitment is a pervasive problem in the IT industry. In this article we take a look at the behaviors that drive over commitment and the dynamics at play in your organization the make it a difficult problem to solve. Finally, we offer some advice to those who suffer from this affliction.

  • Interview with Jan de Baere about the Rise and Fall of an Agile Company

    What happens when a director of a consulting company decides to drastically change the culture? At the Agile Tour Brussels conference Jan de Baere presented the why and how of a company that adopted agile, the journey that they went through, and how it came to a sudden end. InfoQ interviewed him about the agile change approach, culture and trust, and the lessons learned from an agile journey.

  • How to use Workshops to Boost Creativity, Team Commitment and Motivation

    Creativity is a powerful motivator for individuals and teams and it can be taught, trained, and enhanced. These are techniques for enhancing creativity to be used your team’s workshops, and they include brainstorming, playing with puns, role plays and opposites games. These activities get people moving and on their toes, making workshops far more effective than traditional meetings.

  • Interview and Book Review Change Artistry

    The book change artistry is a collection of essays from Esther Derby, Don Gray, Johanna Rothman and Gerald M. Weinberg. The essays cover a variety of topics to support professionals in developing their organizational change skills.

  • The Sustainability Agenda in Kanban

    This first article in the series on the Kanban “nine values, three agendas” model, explores the sustainability agenda: a common approach to Kanban adoption at the level of individuals and teams, often motivated by the need for relief from unsustainable practices and workloads. This sustainability agenda draws on the Kanban values transparency, balance, and collaboration.

  • I’d Rather Be Coding – Writing Things Down

    For lots of reasons, most developers hate writing down anything that isn’t code. The Agile Manifesto deemphasizes documentation, but there are times on a project when a little documentation can go a long way. In this article, we will explore why collaboration over comprehensive documentation shouldn’t mean “NO” documentation – and when you should stop coding and start writing things down.

  • Agile Walls

    BVCs, TOWs and POWs are very important tools in the agile world but what exactly are they? BVCs are Big Visible Charts, TOWs are Things on Walls and POWs are Plain Old Whiteboards – information radiators all. Using the right wallware and the information they provide can make or break an agile team.

  • Agile Fluency: Finding Agile That's Fit-for-Purpose

    The Agile Fluency model is a way of thinking about and planning investments to create the conditions of Agile that best fit your development effort, business need, and customer value. James Shore and Diana Larsen described it in the 2012 article "Your Path through Agile Fluency". This article by Diana aims to helps you to use the Agile Fluency model effectively.

BT