In this third article in the series on agile teams, I'll explore why you want to work in a team, what’s in it for you?
5* waarom is een techniek om de grondoorzaken van een probleem te vinden. Door deze grondoorzaken aan te pakken kun je voorkomen dat vergelijkbare problemen in de toekomst optreden.
Are you a Scrum master? Then I'd like to hear what your favorite books are. Please cast your vote in the book poll below.
Zijn retrospectieves moeilijk, zijn ze lastig om te doen? Nee! Zijn ze waardevol voor teams en organisaties? Jazeker! Het helpt om te weten waarom je retrospectives doet en hoe je ze kunt doen om effectief en continu te verbeteren.
Two Truths and a Lie is a teambuilding exercise using agile coaching cards from the agile self-assessment game where people hear things about agile that their fellow team members believe in ... or not believe in.
Agile talks a lot about self-organized teams, where developers and testers work together to deliver software. In this article, I'll explore what people say when they don't want to work in a team and how you can start working together effectively.
In this article, I'll explore when you can gather the data that will be used as input in the retrospective and discuss the advantages and disadvantages of different approaches.
The book Refactoring 2nd edition by Martin Fowler provides detailed descriptions of refactorings to improve the design and quality of code in small steps.
Have you heard about "doing agile" vs "being agile"? Being truly agile takes practicing, experimenting, and learning by doing. Here's my view of how true agility looks.
Agile talks a lot about self-organized teams, where people work intensively together to deliver software. But what really is an agile team? In this article, I’ll explore how agile teams look and what makes them differ from a group or any other format in which people work together. (more…)
The term "resources" is used in a lot in plans, reports, meetings, and official communication. Most often people are meant when someone says resources. I propose to call them by their name and don't call people resources!
Many useful books have been published on how to do Agile Retrospectives. What are your favorite books? Join the online poll on favorite Agile Retrospectives books!