BT
Older rss
  • 0 Bugs Policy

    by Gal Zellermayer on  Apr 05, 2016 2

    Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.

  • Understanding Quality and Reliability

    by C. Taylor Putnam-Majarian and Doug Putnam on  Mar 23, 2016

    One of the most overlooked but important areas of software development is quality. It often is not considered or even discussed during the early planning stages of all development projects, but it’s almost always the ultimate criteria for when a product is ready to ship or deploy. This article will explore how to measure quality and minimize the factors that negatively impact software reliability.

  • The Way to No-Hotfix Deployment

    by Adam Pahlevi on  Mar 11, 2016 2

    Hot-fix redeployment is a waste of time and effort at best, and often a source of further regression, Adam discusses some ready-to-use techniques that helped he and his team reduce the frequency of hot-fix deployments to almost zero.

Toward Agile Architecture: Insights from 15 Years of ATAM Data

Posted by Stephany Bellomo, Ian Gorton, Rick Kazman on  Oct 17, 2015

The authors have concluded after analyzing 15 years of ATAM data that modifiability, performance, availability, interoperability, and deployability are key quality attributes for Agile practitioners.

The Most Common Reasons Why Software Projects Fail

Posted by Taylor Putnam-Majarian & Doug Putnam on  Jul 13, 2015

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 16

Creating a Culture of Quality

Posted by Jonathan Levene on  Sep 18, 2014

We all want to delight customers with a quality product, and many companies focus on process to reach quality goals. But culture eats process for breakfast. How do you create a culture of quality?

Interview and Book Review: Enterprise Software Delivery

Posted by Craig Smith on  Feb 20, 2013

"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.

Tradeoffs: Giving up Certainty

Posted by Paul Dolman-Darrall on  Dec 20, 2012

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.

My Experience as a QA in Scrum

Posted by Priyanka Hasija on  Jul 17, 2012

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 Developer-Tester Divide

Posted by Gil Zilberfeld on  Apr 25, 2012

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

The Rise of Application Analytics: A New Game Demands New Rules

Posted by Sebastian Holst on  Dec 27, 2011

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.

Implementation Decision Rationales – Program Comprehension in Agile

Posted by Fabian Kiss on  Feb 28, 2011

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

General Feedback
Bugs
Advertising
Editorial
Marketing
InfoQ.com and all content copyright © 2006-2016 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT