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

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

  • Author Q&A: Decoding Silicon Valley

    Jon Baer and Michelle Messina have written a book exploring the secrets to success in Silicon Valley - what it takes for a startup to succeed. They look at the culture, history and stories which show how and why the Valley works, and provide guidance for prospective entrepreneurs who are considering setting up in the Valley, or elsewhere. They spoke to InfoQ about the book and their ideas.

  • Stop Measuring Turn Around Time

    Are you patting yourself on the back for remarkable turn around times while simultaneously neglecting your customers? It's tempting to think that timeliness matters when in fact it rarely does. Stop measuring turn around time and start learning what matters to customers.

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

  • Q&A with Jurgen Appelo on Managing for Happiness

    The book Managing for Happiness by Jurgen Appelo provides practices, games and tools to manage organizations and make work fun. It contains tips and suggestions for applying the practices to achieve organizational greatness and maximize learning in organizations.

  • Why ALM Is Becoming Indispensable in Safety-Critical Product Development

    Integrated Application Lifecycle Management platforms are advancing product development in life and safety critical environments. The story of how Medtronic Neuromodulation were able to modernize their processes using ALM helps us understand current and future trends in the development of complex software-heavy products.

  • Don't Break Your Silos - Push Out the Silo Mentality

    Organizational silos are a serious hurdle for many companies out there. They may cause a wide variety of problems if not dealt with accordingly. Silos may not need to be broken if you manage to push out the mentality that comes with them by creating ventilators. The first step towards dealing with the silos is to learn more about them and familiarize yourself with the best practices against them.

  • Key Takeaway Points and Lessons Learned from QCon New York 2016

    The fifth annual QCon New York was the biggest yet, bringing together over 800 team leads, architects, project managers, and engineering directors. In total, over 140 practitioner-speakers presented 79 full-length technical sessions and 16 in-depth tutorials, providing deep insights into real-world architectures and state of the art software development practices from a practitioner’s perspective.

  • Writing Maintainable Configuration Code

    The article discusses a catalog of configuration smells containing 13 implementation configuration smells and 11 design configuration smells. It provides a few examples of configuration smells along with corresponding refactorings, explains their impact on the quality of the project, and lists a few tools that could be used to reveal such smells.

  • 10 Tools to Help Remote Web Developers Collaborate with Their Team

    Working remotely presents a unique set of challenges for web developers. However, by using the right tools and taking a ‘remote first’ attitude, you’ll find yourself being more productive than teams working face-to-face. Here are 10 tools for bug tracking, collaborative coding and knowledge management.

BT