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

  • Virtual Panel on Bimodal IT

    Bimodal IT has been supported by many and criticized by many. InfoQ reached out to enterprise experts to dig deeper into the pros and cons of this strategy and how/when/if is it applicable.

  • Why Agile Is Critical for Attracting Millennial Engineers

    More and more companies are realizing that having an Agile organization is critical to attracting and retaining the latest generation of millennial engineers. Millennials demand the context, flat organization/decentralized power and emphasis on collaboration that Agile offers – and companies of all sizes and verticals are responding.

  • What Exactly is the Agile Mindset?

    We hear, and even use, the phrase “agile mindset.” But what is it, really? In this article several themes are identified, such as respect, ability to change, and focus on delivering value. Additionally, possible methods for introducing and nurturing these themes are identified.

  • Christine Doig on Data Science as a Team Discipline

    Christine Doig spoke at this year's OSCON Conference about data science as a team discipline and how to navigate the data science Python ecosystem. InfoQ spoke with Christine about challenges data science teams need to address to be more effective.

  • Q&A with Diomidis Spinellis on Effective Debugging

    The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems. It provides methods, strategies, techniques, and tools for finding and removing faults, and gives examples for using them in different settings.

  • So, How Do You Make Agile Successful?

    It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.

  • WTF requirements in Agile Product Development

    The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.

  • Waterfall Requirements in Agile Product Development

    The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.

  • Iterative Prototyping in the Mobile App Development Process

    Mobile app development adopted an iterative, rapid development process and prototypes have a role to play in this agile approach, enabling developers to build, test, iterate, re-test and re-build rapidly and at lower cost (not to mention allowing all stakeholders in the process early on). This article guides through the essential steps of mobile app prototyping.

  • Q&A with Jason Fox on How to Lead a Quest

    In the book How to Lead a Quest Jason Fox explores what can be done to develop insights for strategic decisions and innovation, and for driving progress and delivering value. The book provides approaches and rituals for asking deeper, bigger questions and slow, thorough thinking, creating options and designing experiments for dealing with complexity, ambiguity and uncertainty.

  • Growing Agile… Not Scaling!

    What makes an agile team successful is not the “process” nor the “tools” but rather the way people develop an effective level of interaction with each other. Growing agile means both focusing on culture, and on co-evolution of practices and tools.

  • How to Deal with COTS Products in a DevOps World

    Mirco Hering explains why we shouldn't leave COTS products (and the people working on them) left behind in a DevOps world. With creative solutions we can apply good practices from custom software. This leads to a significant effort reduction in the long term.

BT