Many people dislike the 3 question, plus-minus-delta retrospective. I am one of them. The plus-minus-delta agile retrospective leads to many problems. I say it was never the “standard” in the title, so why are so many people confused? Or…am I the one confused?
While co-coaching recently, the other coach and I had a brief exchange about how the
I was coaching someone a while back and asked them to tell me what their vision statement: what motivated him? When I heard the answer, I was not moved. What I heard was boring. I knew this person had passion for what he did. What happened to it?
If I ask you to tell me why you do what you
I am often asked by folks I’m coaching for ideas of assessments they can take to help them grow.
I’m working on a few articles about different types of assessments and improving yourself. Notice that I did not say “ways to manipulate people!” Sometimes people think the value of these assessments is to control people or
Fist of Five Voting is a deceivingly simple process you can use to check-in, learn, gain consensus, and/or vote to understand where people stand on an issue or idea. I say deceivingly, because there is so much more you can learn about what is really happening in a team if you are paying attention.
I wrote about agile team retrospectives in a recent article and find that the term retrospective can be used in many different ways. I’ve heard people ask, “Did you just change the name from lessons-learned to retrospective?” Although there are similarities, there are some key differences. Let’s review a few types and
I get a lot of questions about agile retrospectives from existing clients who are familiar with agile, those new to it, and folks who don’t use agile (so, yes: everyone!). This is one in a series of posts on retrospectives covering a variety of angles on the subject. [Agile Retrospective Resources has a list
There is a lot of information out there are agile retrospectives. I have a number of articles on them and there are plenty of places with information including blogs, websites, and books.
Will longer agile sprints or iterations cover up opportunities to improve and cause you to view these opportunities as unsolvable problems?
The typical agile sprint size is 2 weeks. What percentage of teams use 2 weeks? I don’t have statistics on it,