The authors have concluded after analyzing 15 years of Architecture Trade-Off Analysis Method (ATAM) data across 31 projects that modifiability, performance, availability, interoperability, and deployability are key quality attributes for Agile practitioners.
Knowing the basics of software development can greatly improve the project outcome; however, that alone is not enough to prevent project failures. Projects can be categorized as failures because of cost overruns, late deliveries or poor quality, but the right estimation processes can increase the likelihood of project success.
Every company wants to delight customers with a high-quality product, and many organizations naturally focus on process improvements to reach quality goals. But organizational culture eats process for breakfast. So how do you create a culture of quality? New research on 850 employees who impact quality from 80 companies presents new strategies for shifting values, norms, beliefs, and habits.
"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.
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
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.
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
Fixed price contracts are often decried as evil, however they are something which many agile teams face. How can a company execute one using agile practices to achieve better results with lower risk? 15
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect? 43
This article takes a look at Edward Deming's work and it's applicability to Agile methods. 2