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

  • Meeting Regulatory Demands with Agile Software Development

    InfoQ interviewed Jan van Moll about regulatory demands for software in healthcare, satisfying these demands with waterfall project or with a mix of waterfall and agile, and introducing agile in an R&D organization that needs to fulfill regulatory demands.

  • Martin Fowler on "Yagni: You Are Not Gonna Need IT" XP Practice

    Martin Fowler describes yagni practice, why its is important and the costs of building presumptive features. Yagni is an acronym that stands for "You Aren't Gonna Need It". It is an Extreme Programming (XP) practice which states a programmer should not add functionality until deemed necessary.

  • Managing Technical Debt Using Total Cost of Ownership

    Total Cost of Ownership (TCO) can be used for investment decisions and financial benefit analysis. When applied to software it covers the initial development costs and subsequent maintenance costs until phase out of a product. TCO can support architectural decisions and management of technical debt.

  • Delivering Business Value

    Calculating the business value of features is way beyond just a few numbers.

  • Agile Australia 2015 to Focus on the Art of Simplicity

    The Agile Australia 2015 conference is running in Sydney on 17 - 18 June with its theme around the art of simplicty. The conference has been running since 2009 and is set to attract over 1,000 delgates representing over 250 of Australia's leading organisations.

  • How to Facilitate an Agile Retrospective Using "Rory Story Cubes"

    How to use Rory Story Cubes for sprint retrospective.

  • Applying Continuous Integration at Thales Naval Systems

    Continuous Integration can help to find integration issues earlier and to visualize the status of the build to all involved. Integration problems can be detected at build-time in stead of run-time during testing and teams can get immediate feedback on changes that they made and on the impact on components that are developed by other teams.

  • The CRM Landscape as Viewed by Teamleader

    Last month, Teamleader won the HenQ award of the Boost competition at The Next Web Europe 2015 in Amsterdam, Netherlands. Benny Waelput from Teamleader discusses about the present and future of CRM systems.

  • How to Descale an Organization

    There are many frameworks available for scaling Agile. In contrast to the concept of scaling Agile, there is a belief of descaling the organization.

  • Founder of API Blueprint Discusses Progress

    API languages are in their infancy and API developers are actively using API Blueprint, RAML, and Swagger. Together, as a community, developers are defining the standards that will be used in the future. InfoQ recently had the opportunity to talk to Jakub Nesetril, creator of the API Blueprint project and CEO of Apiary.

  • Surviving Success

    Teams rarely consider success as a mode of failure, but not preparing for exceeding their goals can be just as dangerous as ignoring basic software and infrastructure needs. Mark Simms and Mark Souza discuss anti-patterns they've seen and some of the best ways to architect to win in spite of your own success.

  • Addressing Organizational Debt

    Steve Blank,talks about the organizational debt which is similar to technical debt. He says that growing companies need to understand how to recognize and refactor the organizational debt.

  • Extending, Defining and Evolving the Understanding of Agile

    Recently there have been a number of posts which challenge the way agile methods have been applied in industry and present some ideas on improving adoption and outcomes by tackling the underlying problems. Andy Hunt proposes a completely new approach branded The GROWS Method(tm) and Dan Greening suggests clarifying the core concepts which underlie agile approaches and describing them for use.

  • Developing Provably-Correct Software Using Formal Methods

    Computer-checked models can be used to prove that core communications and state management in a software program are 100% logically correct. Such models can also be used to generate 100% correct source code. The usage of formal methods can reduce costs and time to market and help to deliver highly reliable software products.

  • Delivering Value on Time by Using #NoEstimates

    Vasco Duarte suggests that people should experiment with #NoEstimates to learn and find ways in which it can help them to deliver value on time and under budget. He is writing a book on #NoEstimates in which he explains why estimation does not work and how you can use #NoEstimates to manage projects.

BT