Lean-Agile Acceptance Test-Driven Development

Published May 20th, 2011 Under Quality | Leave a Comment

Acceptance tests are defined in this book as the test created by the customer in collaboration with the developer and the tester prior to implementation. They are not the traditional user acceptance tests performed after implementation. Although acceptance tests can be used at different development stages, Ken Pugh proposes mainly in this book an approach where all project stakeholders will collaborate to create tests that validate business requirements. Read more

Managing Software Debt

Published February 18th, 2011 Under Quality | Leave a Comment

Technical debt has become a trendy term for an issue that exists since the beginning of software development projects. It is what happens when you neglect, consciously or not, the long-term quality of your software to achieve other usually short term benefits. After defining the concept of software debt, Chris Sterling explores the topic of managing software debt in all software development activities. Three chapters are dedicated to the topic of design and architecture, discussing how they should fit in Agile approaches.

As its title suggests, this book goes even further than the concept of technical debt as it try to cover all dimensions of software development debt. My favorite chapter comes at the end where the notion of experience debt is explored. I have witnessed many projects where the technical or product knowledge was concentrated on fewer and fewer people, due to change in project team composition, effectively making them the bottlenecks where all application evolutions had to be processed. We sometimes create more debt in the heads than in the code.

The book is well written and easy to read. Every chapter begins with a mindmap of the topic that will be explored, thus giving a big picture of its content. The material mixes high level definitions with practical examples and real life stories. A summary is proposed at the end of each chapter

At every stage of the software development life cycle, we make decisions that have long term consequences. This book provides meaningful insights on how to prevent creating too much debt and how to reduce the existing burden. I will recommend it to everybody who is concerned with software quality with a longer view than the end of the next iteration.

Reference: ” Managing Software Debt – Building for Inevitable Change “, of Chris Sterling, Addison-Wesley, 228 pages, ISBN 978-0-321-55413-0

Get more details on this book or buy it on amazon.com
Get more details on this book or buy it on amazon.co.uk

Quotes

“Software debt creeps into systems slowly, allowing both the business and software delivery teams to maintain the illusion of rapid delivery far longer than they should. At some point small form of decay in software become large enough to affect delivery to a point where working harder and longer doesn’t result in successful outcomes.”

“Agile teams should not forget that software development involves more than code and test. The act of releasing software is essential and teams can help to make the act almost a non-event.”

Growing Object-Oriented Software, Guided by Tests

Published April 30th, 2010 Under Programming, Quality | Leave a Comment

Object orientation (OO) is not a trendy concept these days, but it hasn’t certainly lost it values. The purpose of this book is to integrate the development of object oriented software with the test-driven development (TDD) approach, more specifically in Java. It starts with an introduction to TDD and the tools (Junit, jMock2) that will be used. It describes then in detail the TDD process that is then illustrated by a large example. The book ends with more software testing topics like tests smells or tests readability. A final part is dedicated to special aspects of testing like persistence, threads and asynchronous code. Read more

Debug It!

Published February 26th, 2010 Under Quality | Leave a Comment

This book provides a structured approach that will help programmers to identify and remove bugs in code. It is based on a four steps process: Reproduce, Diagnose, Fix, Reflect. For each activity, the author provides practical material on how perform it. The second part gives a higher vision of the debugging process and deal with topics like communicating with users or prioritizing bugs treatment. Finally, the book discusses special situations and the relationship between bugs and other areas of software development (source control, build, etc.). Read more

Implementing Automated Testing

Published May 25th, 2009 Under Quality | Leave a Comment

This book presents a comprehensive treatment of the domain of software testing automation. The first part defines and describes test automation, proposing a business case for automation and discussing the pitfalls that should be avoided. Read more

keep looking »