InfoQ interviewed the authors of fifty quick ideas to improve your retrospectives about why they wrote the book and how ideas are described, when you can do retrospectives, what facilitators can do to establish safety, why facilitators should not be the ones who solve problems, celebrating successes, good practices for getting actions done, and the value that teams get from doing retrospectives.
Book review and interview with Steve Smith and Matthew Skelton, authors of "Build Quality In", a collection of experience reports (including their own) on Continuous Delivery and DevOps initiatives, by authors ranging from in-house technical and process leaders to external consultants implementing technical and organizational improvements.
As infrastructure becomes code, reviewing (and testing) provides the confidence necessary for refactoring systems. Reviews also help spread consistent best practices throughout the organization.
The book Scrumban [R]Evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban explores the principles and theories of Scrumban, and shows how Scrumban can be deployed in organizations. 2
The story of a team who worked on a single screen, had no formally defined roles, performed no estimates, worked on a one task at a time and delivered a quality product to a satisfied customer.
Every developer knows the pain of incompatible software. By using Docker executable images developers can take advantage of container technology to better control their development environments. 1
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.
The "Lean Enterprise" book authors discuss how traditional management practices fail to balance innovation and product exploitation as they require very different sets of capabilities.
Agile software development is in a rut. The most popular agile methods are consistently mis-applied, mis-understood, mis-used, and all too often abandoned. This article proposes a new approach. 1
Óscar San José, technical lead at Tuenti (largest Spanish social network) explains how and why their in-house Flow deployment system allowed developer teams to be more independent and deliver faster.
This article describes the change that was done to support growth at Seamless Payments, based on Agile and Lean values and using a slimmed down version of SAFe that still maintained its core ideas. 4
Mark Levison recently wrote a blog on “Scrum Alone is Not Enough”, which is the first blog of a series to uncover various Agile patterns.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Blog Series: A skeptic's guide to Continuous Delivery