I will give a keynote on the need for continuous improvement on October 13 at Agile Tour Kaunas, the biggest event about agile project management and information systems development in Lithuania.
Since the manifesto for agile software development hasn't changed since it's publication in 2001, the question arises if the Agile Manifesto needs an update. I think it should be updated to reflect what has been accomplished with agile and to state what the software industry needs now.
The XP Days program committee has accepted my workshop “Agile Self-Assessment Game” for the XP Days Benelux 2016 conference. How cool is that!
Building a new team can be challenging. People have to learn and get to know each other, and agree upon how they will be collaborating as a team. Retrospective exercises can be used for chartering teams, to define shared goals, agree upon the way of working, and start off properly.
Agile methoden zoals Scrum leggen de nadruk op functionaliteit. Klanten verwachten echter naast functionaliteit dat ook de kwaliteit van het product in orde is. Waar agile voornamelijk aandacht geeft aan het software team en de interactie met de omgeving, kijkt Lean naar de gehele keten: van klantbehoefte tot waarde voor de klant. Een van de aspecten van Lean Software Ontwikkeling is het integreren van kwaliteit.
Het manifest voor agile veranderen helpt organisaties om hun agility te verhogen. Het zorgt voor blijvende verbetering van de resultaten, tevreden klanten, en blije medewerkers. Dit eerste artikel over Agile Veranderen beschijft de uitgangspunten en waarden met behulp van het manifest voor agile veranderen.
The Trello board retrospective techniques for coaches, Scrum masters, and other facilitators provides exercises and ideas to design agile retrospectives. Philip Rogers created this board, he has added me so that I can contribute my experience with retrospectives. (more…)
In one of my workshops I explored how to use agile and Scrum beyond software development, for example in marketing, sales, support and in management. I gave this workshop in-house for a client to an audience which was not directly involved in software development. Many good ideas came up when preparing and giving this workshop, in this post I'm sharing them with the agile community.
Come to my workshop on Nov 1 in Kladno (near Prague) to make your agile retrospectives valuable. You'll learn the why, what and how of agile retrospectives and practice exercises to develop your facilitation skills.
If I ask people who facilitates their agile retrospective, most tell me that it's their Scrum master. Some even look surprised, as if their could be anybody else who leads their retrospectives? Yes there can be. In some situation it's even better if somebody else than the Scrum master facilitates the agile retrospective.
In my workshops I often play the impediment game with teams. In that game team members discuss impediments that happen during Scrum sprints or Kanban flows, and decide how to deal with them and who should solve the impediment. The "who" is most often "any team member". But in practice I see that teams struggle with impediments, and often expect the Scrum master or a manager to solve them. Let's explore what can be done to have impediments solved by Scrum team members.
