BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Culture & Methods Content on InfoQ

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

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

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

  • Meaning it: What’s the Real Purpose of Corporate Social Responsibility?

    A restaurant to give homeless people apprenticeships? A centre to foster social enterprise? A ‘round the nation’ bike ride? Helen Walton, chair of the Spark Award judging panel, talks to PwC about the range of their charitable activities in the UK, and why they’re about business, not image.

  • A Focus on Agile Principles over Agile Rituals

    When scaling agile principles through rituals it's important to constantly evaluate and evolve those rituals. This article provides examples of experiments that focus on the original intent when developing team behaviors. It shows how you can be aware of triggers that mean your team is not finding value in a ritual and what you can do to make things more visible.

  • Voys Learns to Play the Holacracy Game

    Holacracy removes power from a management hierarchy and distributes it across teams that have a clear set of roles, responsibilities, and expectations. This new organizational system with no managers or titles is often misunderstood. Learn about holacracy from the Dutch telecom company Voys who implemented this new way of running organizations.

  • The Lean Business Analysis Manifesto Explained

    David Morris explains how Lean Business Analysis responds to the ever-increasing pace of change in an age of digital disruption. We no longer have business as usual, so why would we do business analysis as usual? The Lean Business Analysis Manifesto helps put order into the chaos that exists in many of today’s organisations.

  • Understanding Quality and Reliability

    One of the most overlooked but important areas of software development is quality. It often is not considered or even discussed during the early planning stages of all development projects, but it’s almost always the ultimate criteria for when a product is ready to ship or deploy. This article will explore how to measure quality and minimize the factors that negatively impact software reliability.

BT