What if we fail?

People are often afraid to make mistakes. They do things to prevent that something might go wrong and avoid doing things that might fail. And if it does go wrong then they don't talk about it. Is it really bad if once in a while something goes wrong? If something can go wrong, let arrange for it to happen as soon as possible, because then you can quickly learn from it. Create a culture where failure is allowed so that we can all learn from it and find ways to make fewer mistakes!

Continue Reading

Empower Teams to Increase Quality

When an organization is experiencing quality problems with their products, agile software development often isn't the first solution that comes up in people's minds. Often I see people trying to address them using classical waterfall based approaches, only to find out that it will make problems even worse. I recommend agile, not only to deliver working software faster but also with the right quality. This posts shows how empowering the team helps to increase the quality of product.

Continue Reading

Success Factors for Root Cause Analysis in Software Development

Root Cause Analysis can be used in software development to build a shared understanding of a problem to determine the first or “root” causes. Knowing these causes helps to identify effective improvement actions to prevent similar problems in the future. You can also do Root Cause Analysis in agile to stop problems that have been bugging your team for too long.

Continue Reading

Agile Veranderen door sterktes te gebruiken

De trend die ik in 2013 heb gezien van kleinere en snellere verbeteringen in organisaties zal zich doorzetten in 2014. Een Agile manier van veranderen, mbv Scrum, maakt het mogelijk om samen te verbeteren: medewerkers en managers. Het stimuleert zelf-organisatie en benut de kracht van de medewerkers om organisatiedoelen te bereiken. We gaan het gewoon doen in 2014: Sterktes gebruiken om op een Agile manier te veranderen!

Continue Reading

Continu Verbeteren: Benut je Sterktes!

Agile projecten gebruiken vaak retrospectives, waarin ze vragen stellen zoals: 'wat gaat er goed', en 'wat kan beter'? Met het eerste gebeurd vaak niet zoveel. 'Leuk om te horen' is de reactie. Een gemiste kans! Want weten wat er goed gaat en begrijpen waarom, de onderliggende sterktes, kan je helpen om dingen te verbeteren die (nog) niet goed gaan.

Continue Reading

Using Solution Focused in a Strengths Based Retrospective

How can you become an excellent team that is able to deliver and exceed customer expectations? By continuously becoming better in the things that you are doing great, using a strengths based retrospective. This technique helps teams to improve themselves by focusing on their personal and team strengths.

Continue Reading

The Economics of Software Quality

The book Economics of Software Quality provides solutions to quantify Software Quality and manage software development and maintenance. It contains data usable to build a business case to improve quality, and decide upon improvements in your organization.

Continue Reading

En wat als het nou fout gaat?

Is het wel zo erg als er een keer iets fout gaat? Als het fout kan gaan, laat dat dan maar zo snel mogelijk gebeuren, want dan kun je er van leren. Creëer een cultuur waarin falen mag, samen op weg naar minder fouten!

Continue Reading
Close Menu
×
×

Cart