BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Software Craftsmanship Content on InfoQ

  • Applying Lean Thinking to Software Development

    Lean’s major concept is about reducing waste, meaning anything in your production cycle that is not adding value to the customer is considered waste and should therefore be removed from the process. Steven Peeters explains how you can apply Lean principles in an IT environment.

  • Book Launch of “Commitment”, and an Interview with Olav Maassen, Chris Matts and Chris Geary

    Commitment is a graphical business novel about managing project risks with “Real Options”, a way of thinking to improve your decision making. InfoQ attended the book launch on May 14 in Amersfoort, The Netherlands and spoke with the authors about decision making, risks and technical debt.

  • Interview with Capers Jones on Measuring for Agile Adoption

    Why would you want to use measurements if you are adopting agile? Because top executives would like to know how projects will turn out before spending money on them, and measuring results helps to improve future predictions. Capers Jones shows how you can measure productivity and quality, and looks at agile practices that have proved to be beneficial for teams.

  • Interview and Book Review: Enterprise Software Delivery

    "Enterprise Software Delivery" is the latest book by Alan W. Brown, and is a must-read guide for anybody concerned with the development and delivery of software in a large organisation.

  • Tradeoffs: Giving up Certainty

    While organizations operate under an illusion of certainty, tradeoffs are inevitable. Giving up certainty does not mean giving up predictability. This article examines four flow choices for software delivery and presents three choices for IT Delivery: Throughput, Flexibility and all out speed.

  • Automated Error Reporting: The Gateway to Better Quality

    Ignorance might be bliss, but it goes straight to the bottom line when it comes to software bugs. Those who can ferret out bugs and improve the quality of their software will be rewarded with greater customer trust, higher renewal rates, lower maintenance costs, and fewer opportunities for the competition. Laila Lotfi explains how automated error reporting aids in this endeavor.

  • Using Kanban to Turn Around Distressed Projects

    This case study describes how Kanban and lean development techniques were used to rescue a distressed project that had violated its budget, schedule, and quality constraints. The article presents a detailed account of how the techniques were introduced mid-project to establish control over a chaotic project environment, and is supported with several charts that show the team’s progress.

  • My Experience as a QA in Scrum

    The QA role in Scrum is much more than just writing test cases and reporting bugs. In this article, Priyanka Hasija shares her experiences and the valuable lessons learned over the past 2 years while serving as a QA analyst on a Scrum team. She explains how QAs not only perform agile tests but also fill many other roles and responsibilities, earning them a place of importance on the team.

  • The Developer-Tester Divide

    The evolution of the software industry has created two separate roles: The developer and the tester. Traditional software development put these two at odds. Now, agile practices are bringing them together again in order to meet the original business goal: working software.

  • Faster, Better, Higher – But How?

    One of the main challenges when designing software architecture is the consideration of quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes. Consequently, many problems in software systems are directly related to the specification and design of quality attributes such as modifiability or performance, to name just a few.

  • The Rise of Application Analytics: A New Game Demands New Rules

    When developers know how their applications are really being used “in the wild,” they will build better software, more efficiently, and with greater confidence. Sebastian Holst shows you how using application analytics.

  • Trust is good, Control is better - Software Architecture Assessment

    Testing is an important means to obtain information about implementations. Likewise, code reviews help to keep the code quality high. What is very common for code, gets sometimes neglected for software architecture. But how can a project team test the architecture itself? Software architecture assessment represents an effective approach for introspecting and assessing software design.

BT