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.
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.
Giving up certainty doesn't mean giving up predictability. This article examines 4 flow choices for software delivery and presents 3 choices for IT Delivery: Throughput, Flexibility & all out speed.
Laila Lotfi explains how using automated error reporting results in greater customer trust, higher renewal rates, lower maintenance costs, and fewer opportunities for the competition. 2
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. 13
The QA role in Scrum is much more than writing tests and reporting bugs. In this article, Priyanka Hasija shares her experiences and the valuable lessons learned while serving as a QA in Scrum. 32
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. 2
One of the main challenges when designing software architecture is considering quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes. 2
When developers know how their applications are really being used “in the wild,” they will build better software. Sebastian Holst shows you how using application analytics.
Testing is an important means to obtain information about code. What is common for code, can't be neglected for software architecture. This is where software architecture assessment comes to help. 2
Gojko Adzic has written Specification by Example in which he provides advice and guidelines on adopting this approach as a way to create living documentation on a software development project. 7