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.
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.
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.
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
This article draws an analogy between QoS for networks and for applications, resulting in a mapping guide between the two and introducing a production solution for Java, (J)Ruby, and (J)Python apps.
James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility. 3
In this article, author Olivier Gaudin discusses the differences between internal and external software quality and how to perform the software quality assessment using Sonar and JaCoCo tools. 2
Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to tie the source code to its meaning in the application domain. 4