“You can’t do 2-week iterations with hardware!” This is the first thing you’ll hear when talk turns to Agile methods in hardware-software product development. A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around - or through - the challenge of doing fast iterations.
At then recent Agile Singapore conference James Grenning presented two technically focused talks - one on the importance of technical excellence and the other teaching test driven development. He spoke to InfoQ about the importance of strong technical practices to enable true agility in software development.
The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.
Scott Ambler discusses a recent mini-survey designed to find out how TDD is being used in practice. He examines the state of practice and what techniques and tools are being used with TDD.
When and how to apply architecture depends on the context. This article shows how you can give proper attention to architecture in an agile setting. Adaptability and conversation are the essentials. 4
An interview with Tim Ottinger and Ruud Wijnands about the way that organizations adopt agile, services provided by the industry, and the importance of technical practices and craftsmanship in agile.
Michał Bartyzel challenges the need to master a *Driven* approach to be Software Professional. These might be: DDD, TDD, BDD, MDD or other frameworks which can be responsible for cognitive biases. 7
Quality Code book covers different aspects of SDLC with focus on delivering quality product. InfoQ spoke with author Stephen Vance about the book and best practices for testing applications.
The second edition of Stephen Nelson-Smith's book "Test-Driven Infrastructure with Chef" describes a testing workflow and tools for writing fully tested infrastructure code
A concrete example of how to get started with acceptance-test driven development on an existing code base. It is part of the solution to technical debt. 5
“ATDD By Example” value proposition was to be an introductory hands-on guide to implementing and successfully applying Acceptance Test Driven Development (ATDD) from zero.
In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development. 9