Capers Jones wrote the book The Technical and Social History of Software Engineering in which he provides an overview of the evolution of information technology and software development. InfoQ interviewed Capers about advancements and events in software engineering and the effects that they have had on our society.
Quality Code book, authored by Stephen Vance, covers the different aspects of software development lifecycle with focus on delivering quality product. In the book, Stephen discusses the practices for supporting software craftsmanship testing. InfoQ spoke with the author about the book and the best practices for testing application code.
Handling Technical Debt in a software system is a complex challenge. Code can always be improved – but customers only care about features. This article discusses the new metaphor “Quality Investments”. It helps to better communicate the quality of the system and guide improvements by focusing on their pay off and return of investment.
Some 80% of all improvement and change programmes fail. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.
This article shares a simple technique used to address problems such as a system’s intended functionality but also qualities such as performance, reliability, portability, and availability.
Lean’s major concept is reducing waste: removing anything that is not adding value to the customer from the process. Steven Peeters explains how you can apply Lean principles in an IT environment. 2
Capers Jones shows how you can measure productivity and quality, and looks at agile practices that have proved to be beneficial for teams. 1
"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.
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. 33