At the start of the 21th century I did my first agile retrospectives. I started with retrospectives to help a project to improve along the way, so that we could reap the benefits during the project, and benefits. My aim then and now: To enable teams and the whole organization to improve continuously.
Wat kan Scrum doen voor de kwaliteit van producten en diensten, en hoe kan samenwerking met de gebruikers zorgen voor een betere kwaliteit?
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.
In deze gastblog laat Wendy Geurkink zien wat organisaties kunnen doen om klantgerichter te worden, en hoe co-creatie en samenwerking dmv the workimprovers connection daaraan bijdraagt.
IT is viewed by many people as being something technical. They have a vision of managers with lot's of plans, documents and spreadsheets, and nerds that are sitting behind their computer doing the "real work". It may be out there, but I don't see it that often. What I see are people working together to deliver software solutions that work, which help their customers in their daily work, and deliver business value to the company. Communication and collaboration are essential to make people and teams successful. So for me, soft skills really matter in IT!
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!
A list of the success factors that helped organizations to get Scrum implemented and used, and to make a difference.
Having a "toolbox" of retrospectives helps you as a retrospective facilitator to deliver value to a team. You can plan a retrospective meeting, and think about the technique that you want to use, but be open to change it on the spot when needed.
To do small changes, or to get an improvement journey started in an organization, I use a short cycled "observe and change" approach, that consists of a couple of hours of observation with a 1 page feedback and change advice.
Hoe ziet organisatie eruit zonder hierarchie en managers, waarin iedere medewerker vrij kan beslissen wat hij/zij wel of niet doet. Een kijkje in de keuken van een Self-Organizing Organization, en de succesfactoren van self-organizing.
One technique often used in agile retrospectives is to ask questions to the Scrum team. It's a technique that is easy to learn, but the effectiveness depends on the questions that you ask to the team. Which Questions do you ask?
Mijn drive is om mensen en organisaties te helpen om continu beter te worden in wat ze doen. Hoe zorg ik voor verbetering? Door te leren dat het anders kan, en te beleven hoe dat is.