InfoQ Homepage Quality Content on InfoQ
-
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.
-
QoS for Applications: A Resource Management Framework for Runtimes
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.
-
Agile Architecture Interactions
James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility.
-
Bridging Internal and External Software Quality with Sonar and JaCoCo
In this article, author Olivier Gaudin discusses the differences between internal and external software quality and how to perform the software quality assessment using tools like Sonar and its new extension JaCoCo.
-
Implementation Decision Rationales – Program Comprehension in Agile
Given the fact that the bulk of a developer's work is maintaining and enhancing existing code, Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to help later developers tie the source code syntax to its meaning in the application domain. Using simple tags and clearly thought out rationale to provide just-enough value.
-
Agile Team Meets a Fixed Price Contract
Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions.
-
Are You a Software Architect?
The line between development and architecture is tricky. Some say it's fake, that architecture is an extension of the design process undertaken by developers; others say it's a chasm that can only be crossed by lofty developers who believe you must abstract your abstractions and not worry about implementation details. There's a balance in the middle, but how do you move from one to the other?