I'm updating and expanding my successful second book What Drives Quality. Intermediate versions are released through Leanpub: What Drives Quality.
I'd like to receive your feedback on my second book What Drives Quality to update it and publish the second edition.
The book The Stupidity Paradox provides suggestions to counter stupidity and reduce the consequences, exploit it, and benefit from it.
Agile retrospectives can be used to investigate quality issues or to agree upon actions that can improve the quality of the software that is delivered.
I've been interviewed on InfoQ about the release of my new book What Drives Quality. Book is available on Amazon, Leanpub, my webshop, and major bookstores.
My 2nd book What Drives Quality has been officially released today (September 30). It is now available on Amazon and all other major bookstores.
My 2nd book What Drives Quality is now available for pre-order on Amazon, Leanpub, and my webshop. The book will be released end of September.
I'm honored to have been interviewed by Tom Cagley for his Software Process and Measurement Cast (SPaMCAST). Tom and I talked about the need for continuous improvement and how agile teams can develop skills and practices to recognize and deal with impediments.
In this third post in the series on handling impediments I'll explore what you can do to understand the impediment and underlying the problems that the team is trying to deal with. Previous posts explained why impediments matter and how you can recognize the problem.
This second post in the series on handling impediments builds on the process described in Handling Impediments: Why it Matters! I'll dive into the first step: recognizing the problem.
Een sterk punt van een agile aanpak is dat dat er in korte cycli, z.g. iteraties of sprints (Scrum) gewerkt wordt, en er steeds feedback momenten zijn. Het cyclisch werken met feedback zorgt ervoor dat het proces bewaakt kan worden, en informatie uit de feedback helpt om continue de agile werkwijze te verbeteren. Dit artikel beschrijft welke feedback er in agile is en hoe je die feedback effectief kunt benutten.
I sometimes hear of teams that have stopped doing retrospectives because they didn't see any improvements. When I talk with them it often turns out that they didn't have good actions coming out of the retrospectives, or that the actions weren't done and kept coming back in the retrospective. No actions leads to no improvement. Here are some suggestions on what you can do to assure that you will have actions from retrospectives that are doable and that those actions get done.