This is the fourth article in a mini-retrospectives series. In the previous ones I wrote about how retrospectives should be done at regular intervals, but also in other occasions and how the retrospective could be done in different groups than just the team and that sometimes changes happen even without an action item being clearly … Weiterlesen …
This is the third article in a mini-retrospectives series. In the previous ones I wrote about how retrospectives should be done at regular intervals, but also in other occasions and how the retrospective could be done in different groups than just the team. In this post I will continue to challenge the 12th principle of … Weiterlesen …
This is the second article in a mini-retrospectives series. In the previous one I talked about how retrospectives should be done at regular intervals, but also in other occasions. In this post I will continue to challenge the 12th principle of the agile manifesto to explain other ways to spice up your retrospectives. The 12th … Weiterlesen …
This is the first in a series of posts about how to moderate retrospectives creatively. Traditionally the retrospective in agile software development is the reflection done at the end of the iteration. Principle twelve of the Agile Manifesto says “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts … Weiterlesen …
While reflecting on my recent activities, I started to recognise an interesting pattern regarding the role of the Product Owner. I’ve seen many of them coming from different parts of the organisations: form product management, from various levels of management, from system architecture or senior programmers. Because of the different skill sets they have, the … Weiterlesen …
Suppose you need to choose the ScrumMaster for your team and there is no „natural“ candidate available. Suppose you have two alternatives who could do the job, but you are not sure who fits best? I got a similar question proposed some time ago by one of my customers. Instead of giving my answer, I … Weiterlesen …
As you have probably noticed – in case you did not fall asleep while reading these pages – I am a strong believer in the solution focused approach and I wrote already several articles about it (see this and this and this). The approach generated interest in many of my peers, so over time I … Weiterlesen …
So the definition of done of a Scrum team is sick and you, dear agile coach, are intervening on the team to get them to fix it. Easy, isn’t it? Either you tackle the issue during a retrospective or on in ad-hoc discussion, point out the symptoms, ask the team how they plan to fix … Weiterlesen …
Have you ever wondered what makes Agile so special and so productive? My guess would be because it closes loops and allows fast and useful feedback. Extreme Programming is all about feedback, openly stated: pair programming, regression testing, continuous integration are all ways of generating the right feedback. Scrum is also based on feedback loops: … Weiterlesen …
Sie sehen gerade einen Platzhalterinhalt von Facebook. Um auf den eigentlichen Inhalt zuzugreifen, klicken Sie auf die Schaltfläche unten. Bitte beachten Sie, dass dabei Daten an Drittanbieter weitergegeben werden.
Mehr InformationenSie sehen gerade einen Platzhalterinhalt von Instagram. Um auf den eigentlichen Inhalt zuzugreifen, klicken Sie auf die Schaltfläche unten. Bitte beachten Sie, dass dabei Daten an Drittanbieter weitergegeben werden.
Mehr InformationenSie müssen den Inhalt von reCAPTCHA laden, um das Formular abzuschicken. Bitte beachten Sie, dass dabei Daten mit Drittanbietern ausgetauscht werden.
Mehr InformationenSie sehen gerade einen Platzhalterinhalt von X. Um auf den eigentlichen Inhalt zuzugreifen, klicken Sie auf die Schaltfläche unten. Bitte beachten Sie, dass dabei Daten an Drittanbieter weitergegeben werden.
Mehr Informationen