Comment

The Agile Project Manager—The Secret Sauce: Team Appreciation

I was attending a session at the Agile 2011 conference where Jean Tabaka from Rally Software was talking about some generic agile coaching tools & techniques. Jean happened to mention a few times that Rally had been internally focused on some organizational change models that happened to focus on strengths, positive recognition, and appreciations.

Focusing in on appreciations, she stated that it started in team retrospectives. That Scrum Masters would ask the teams to share their appreciations of each other as a start-up or entry ceremony for each retrospective. But then it caught onto other organizational meetings. She mentioned that many of their company-wide, all hands meetings began with appreciations.

Comment

1 Comment

The Agile Project Manager—There is no ‘I’ in Team

A couple of weeks ago I was teaching a group new to agile some of the basics surrounding Scrum and related agile practices. It was going well. And, as is sometimes the case, I was getting full of myself and feeling over confident. Things were going smoothly, the attendees were “getting agile”, and life was very good.

Then it happened—from left field and without warning.

We were talking about the nature of a self-directed agile team. I was trying to paint the picture of group-based accountability and responsibility. How empowering it was and how it led to the best results. How teamwork, well basically ‘Rocked’, and how agile teams truly collaborated around the customer to deliver creative and high-quality solutions.

1 Comment

Comment

The Agile Project Manager—Getting out of Jail Free

I was teaching a class just a few weeks ago. It was focused on agile basics, user story writing & backlogs, sprint planning and all of the basic operations to kick-off a set of Scrum teams. It was going quite well on the first day and I was fielding the myriad of questions that typically come your way in an initial class of this sort.

Then I got hit with a question that I struggled to effectively communicate a succinct and direct answer to. The question was simple on the surface:

If within a sprint the team can’t seem to get the work they planned done, don’t you simply put it back on the backlog for execution in the next sprint?

Comment