back to top

our blog


agile teams

Solving Symptoms

by Esther Derby, 23 August 2011

Recently, I attended two retrospectives.  Different teams, different states, different facilitators. I’m usually on the other side, leading retrospectives. Both retrospectives followed the “make lists” pattern.  One made two lists  “What worked well” and “What didn’t work well.”  The other made three lists “What worked well,” “What didn’t work well,” & “Issues or questions.” Once [...]

Tell me more >
Productive Meetings: 1, 3, many

by Edge of Chaos | Agile Development Blog, 22 August 2011

Do you know how to run a really productive meeting? I don’t. I’m learning, and I run meetings with various success so far. My most recent insight is related to the size of a meeting group. Let’s evaluate various sizes and identify str...

Tell me more >
Where should I sit?

by Mike Caspar, 22 August 2011

Inevitably, there will be some change to your team.  Someone will leave or perhaps you will have new members joining you. Either way, you will be asked the question “Where should I sit?”. Do not take this question lightly.  You have the opportunity to make significant changes with the addition or departure of a team [...]

Tell me more >
The Michael Phelps attitude

by Joe Little, 15 August 2011

Whatever thing we do, what is our attitude?  In work or in much of the rest of life, I think our attitude should be some interesting combination of humble and aggressive. My business is lean-agile-scrum.  Are we ever finished learning Scrum ...

Tell me more >
Specialized Skills

by George Dinwiddie, 01 August 2011

Whether we’re talking about revolutionary new web services, IT systems to automate internal procedures, or products to sell in boxes, there are many different sorts of things that need to be done. We need to envision the product, decide what’s required to be done, design it, build it, make sure it works, and put it [...]

Tell me more >
Protecting the Team Cuts Both Ways

by Mike Cohn, 26 July 2011

It is a generally accepted Scrum dictum that one of the ScrumMaster’s duties is to protect the team. The usual example is that the ScrumMaster must protect the team from an overly aggressive product owner. There is nothing wrong with this example and many teams do need to be protected from a product owner whose [...]

Tell me more >
Process Metrics

by George Dinwiddie, 25 July 2011

My good friend Jack Ganssle commented over at EETimes (also available on the TechOnline India site, with different comments) about my recent post on process standards.  In it, Jack cautions against relying on “a strong feeling that ‘things are better.’” He recommends using measurements to bring it back to the realm of engineering. Bob Pease, [...]

Tell me more >
Misconceptions about Self-Organizing Teams

by Esther Derby, 19 July 2011

At a recent conference, I over-heard three managers talking about self-organizing teams. “You can’t just turn people loose and let a team make all the decisions. They’ll mess things up. And with all these ScrumMasters, coaches, and self-organizing teams, sounds like I’m out of a job,” said one with resignation. “This time boxing thing is [...]

Tell me more >