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

  • Production Like Performance Tests of Web-Services

    Tests should always keep the end user view in mind. But how to test web services, which are not directly customer-facing, and in particular, how to performance test them in a meaningful way? This article outlines performance split testing as a performance test approach that is relying on real-time production traffic.

  • Why Won’t They Pair?

    Pair programming is one of the core techniques of eXtreme Programming and has been shown to be effective for knowledge sharing as well as code quality, but it is a practice that is often not used, even in the most agile of organizations. Linda Cook explores why that is and provides some advice on how to encourage teams to try the practice.

  • Q&A on Achieving Impact through Engagement

    The book achieving impact through engagement by Si Alhir and and Peter L. Simon explores two models on employee and customer engagement: The Ownership Pyramid (TOP) and Artful Agility or Actions-Intentions-Results (AIR). Together these models can be used to achieve impact in organizations based on increasing engagement.

  • Q&A with Dave Snowden on Leadership and Using Cynefin for Capturing Requirements

    Dave Snowden gave a talk titled "Context is Everything" at the Scaling Agile for the Enterprise 2016 congress in Brussels, Belgium. InfoQ interviewed him about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.

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

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

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

BT