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: they did not achieve the expected results, the investment in the change programme was greater than the value achieved, “improvements” were seen as mostly bureaucratic, or changes were abandoned soon after the implementation. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.
Often, requirements elicited from stakeholders describe a system’s functionality but fail to address qualities such as performance, reliability, & availability. Documenting these requirements is often overlooked because there are implicit assumptions that the system will perform to expected levels. This article describes a process developed on the idea of persona sketches to address this problem.
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
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