InfoQ Homepage Software Craftsmanship Content on InfoQ
-
/articles/strategy-handling-defects/en/smallimage/agile-logo.jpg)
Now or Never: the Ultimate Strategy for Handling Defects
How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.
-
/articles/book-review-scrum-field-guide-2nd-edition/en/smallimage/logo.jpg)
Q&A on the Scrum Field Guide - 2nd Edition
The Scrum Field Guide - 2nd Edition by Mitch Lacey is a "what to expect" book for organizations transitioning to agile, which aims to help teams to deal with issues that occur and fine-tune their own implementation. An interview about the essentials of Scrum, sprint length, full time Scrum masters, making time available for solving defects, preventing bad hires, and increasing benefits from Scrum.
-
/articles/0-bugs-policy/en/smallimage/fig0.jpg)
0 Bugs Policy
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.
-
/articles/understanding-quality-reliability-qsm/en/smallimage/logo-agile.jpg)
Understanding Quality and Reliability
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.
-
/articles/no-hotfix-deployment/en/smallimage/logo-agile.jpg)
The Way to No-Hotfix Deployment
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.
-
/articles/agile-approaches-test-planning/en/smallimage/agile-logo.jpg)
Agile Approaches in Test Planning
At Agile Testing Days 2015, Eddy Bruin and Ray Oei explained how to satisfy the needs of stakeholders who ask for test cases, test plans, and other comprehensive test artifacts without writing large test plans. An interview about test plans in agile, how to make stakeholders aware that they can influence quality, and which agile practices they recommend for testing.
-
/articles/faster-smarter-devops/en/smallimage/devops-logo.jpg)
Faster, Smarter DevOps
Moving your release cadence from months to weeks is not just about learning Agile practices and getting some automation tools. It involves people, tooling and a transition plan. Derek Weeks discusses some of the benefits and approaches to getting there.
-
/articles/book-review-the-agile-mindset/en/smallimage/cover.jpg)
Q&A on The Agile Mind-Set
Gil Broza explores agile values, beliefs and principles, and explains how they can be used to drive agile adoption in his book The Agile Mind-set. The book provides ideas, examples, and anecdotes that organizations can use to make a shift to agile.
-
/articles/atam-quality-attributes/en/smallimage/ieee-image.jpg)
Toward Agile Architecture: Insights from 15 Years of ATAM Data
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.
-
/articles/book-review-kanban-change-leadership/en/smallimage/cover3.jpg)
Q&A on Kanban Change Leadership
In the book Kanban Change Leadership Klaus Leopold and Sigi Kaltenecker explore how Kanban can be deployed to get change done in organizations and to build a culture of continuous improvement. An interview on doing change in small steps, solving problems, using WIP limits, priorities and classes of service in Kanban, using the Theory of Constraints with Kanban, and getting results with Kanban.
-
/articles/agile-value-delivery/en/smallimage/Front-Cover.png)
Author Q&A on Agile Value Delivery - Beyond the Numbers
Larry Cooper and Jen Stone have written a book which provides advice and techniques for blending agile practices with portfolio, program and project management, taking a value focused approach to managing the outcomes of initiatives rather than focusing on the activities and practices which are the center of many methodologies. They spoke to InfoQ about the book and the ideas behind it.
-
/articles/software-failure-reasons/en/smallimage/logo-agile2.jpg)
The Most Common Reasons Why Software Projects Fail
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.