I started working freelance with SearchSoftwareQuality to share my experiences with Agile, Quality and Continuous Improvement. SearchSoftwareQuality is an online community provided by TechTarget, a leading online technology media company.
I have collected research, studies and reports that provide insight into the business benefits of agile in a new agile and lean tool: Business Benefits of Agile.
One of the principles from agile and lean software development is transparency. Making things visible helps teams to decide what to do and to collaborate effectively with their stakeholders. It can also help to increase the quality of software. This post provides ideas how you can do that.
The book Wartościowe Retrospekcje Agile has been released on Leanpub. This is the 8th translated edition of the successful book Getting Value out of Agile Retrospectives.
The Belarusian and Russian translations have been added to the blog post Retrospective Prime Directive in many languages. This post now contains 11 translations of this important statement that is used in Agile Retrospectives all over the world.
The Scrum Alliance has published the 2015 State of Scrum Report. You can download the full report from the Scrum Alliance website.
On October 22 I will do a full day workshop Valuable Agile Retrospectives at Agile Tour London. For registration please see the Agile Tour London training page.
In this guest blog post on BenLinders.com David Horowitz, CEO and Co-Founder of Retrium, explores why you should do continuous agile retrospectives and how you can do them to establish continuous improvement.
Do you have the same person acting as a Scrum master for every iteration in your team(s)? Or do different team members take the role on turns? I'd like to hear how you do it, what works for you, and why.
The Leanpub bundle Agile Retrospectives offers great books to do amazing Agile Retrospectives. Together these books will make your Agile retrospectives rock! Teams will love to do them :-) And now you can get these books with a significant discount :-).
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.
The retrospective prime directive is a sentence that is used by facilitators to establish safety in a retrospective meeting. Safety is crucial if you want people to speak up and be open, which is an important precondition to reflect and learn which is what agile retrospectives are all about. Since our book is being translated into many languages we now have translations of this unique and important statement.